Instructions on how to update the formula/the bottles to a new release of a library about homebrew-formulae

[francesco-romano]

For the Bottle part, I started this section: https://github.com/robotology/homebrew-formulae/wiki/How-to---Homebrew#generate-bottles

[claudiofantacci]

I don't think resources are what we really need. I think I used them for the rFSM formula.
For now, I think we should make a choice for master and devel and stick to that.
Note that homebrew supports also unstable code. Unfortunately, that cannot be a git branch, but only an archive :(

I would stick to master now until we are 100% capable of handling YARP-dependency master-master and devel-devel branches installations.

The comment you posted seems to indicate that at least for the CPU part, the bottle should be compatible with old CPUs. Probably the easiest thing is to experiment a bit

That is correct and I agree.

[claudiofantacci]

Basically the two documentation pages are:

1. make a new release
2. make a bottle

They contain more than the concise steps to update formulae/bottoles, but most of what is needed is there.

Maybe we could just take what is needed and create a section under the Wiki tab.
What do you think about it?

[drdanz]

I'm not sure if we still want to support el capitan, but in case let me know and I can generate the bottles for this release...

[francesco-romano]

@drdanz one thing that should be checked if it is possible to generate bottles on newer machines targeting older ones. This should simplify a lot the deployment.
I don't see why this should not be possible (all macOS stuff has a deployment target option), but I was not able to find this option in the brew bottle command

[claudiofantacci]

The only information I found for this is

By default, bottles will be built for the oldest CPU supported by the OS/architecture you’re building for. (That’s Core 2 for 64-bit OSs, Core for 32-bit.) This ensures that bottles are compatible with all computers you might distribute them to. If you really want your bottles to be optimized for something else, you can pass the --bottle-arch= option to build for another architecture - for example, brew install foo --bottle-arch=penryn. Just remember that if you build for a newer architecture some of your users might get binaries they can’t run and that would be sad!

Which I don't think is what we would like to do.
What would be desirable is to be, say, in High Sierra, and generate bottles for Sierra, El Capitan, Maveriks ecc. Am I right?

As far as download-and-install-additional-resources section is concerned, I was unaware of this and I must say that the documentation and the syntax itself is notthat straightforward (and I'm not a Ruby dev). Anyway, if this is actually possible we may want to even add an option to build everything in devel.

[francesco-romano]

I don't think resources are what we really need. I think I used them for the rFSM formula.
For now, I think we should make a choice for master and devel and stick to that.
Note that homebrew supports also unstable code. Unfortunately, that cannot be a git branch, but only an archive :(

The comment you posted seems to indicate that at least for the CPU part, the bottle should be compatible with old CPUs. Probably the easiest thing is to experiment a bit