Hello homebrew users, It seems during the first two or three days of my homebrew usage, I did find how to "brew upgrade outdated", upgrading all packages which have an updated formula since their previous build, but now I missed it. just seen cmake updated, but "brew install cmake" tell me cmake is already installed and "brew upgrade outdated" does nothing. thanks for the tip.
On Jul 25, 2011, at 4:29 PM, Philippe Strauss wrote: > "brew install cmake" tell me cmake is already installed and > "brew upgrade outdated" does nothing. in this case only the formula was updated, but the installed version of cmake was not (it's still 2.8.5). (in this specific case it was updated to have a patch to better support qt libraries, if that's of interest you'll have to uninstall cmake and reinstall) this does make a good point that maybe there should be a different indicator showing when a formula is updated in the event there's no updates to be installed as a result.
Hi, Philippe, You don't need "outdated" - the command is just "brew upgrade". On Mon, Jul 25, 2011 at 4:29 PM, Philippe Strauss <philou@philou.ch> wrote: > Hello homebrew users, > > It seems during the first two or three days of my homebrew usage, I did > find how to > > "brew upgrade outdated", upgrading all packages which have an updated > formula since their previous build, but now I missed it. > > just seen cmake updated, but > > "brew install cmake" tell me cmake is already installed and > "brew upgrade outdated" does nothing. > > thanks for the tip. >
Hi.
On 25 Jul 2011, at 22:33, Misty De Meo wrote:
> You don't need "outdated" - the command is just "brew upgrade".
Some questions :
1. If I have a bunch of packages installed with specific options, will a
'brew upgrade' respect those options while upgrading ? Or do I have to
revert to multiple manual 'brew install's with the options of interest for
each outdated package ?
2. Why don't I see 'brew upgrade' in the brew manpage ? Is it a 'devel'
feature of some sort ?
Cheers,
Robin
> 2. Why don't I see 'brew upgrade' in the brew manpage ? Is it a 'devel'
feature of some sort ?
Brew upgrade is a hack. I am actually just finishing up the proper
command, finally.
It never got written as people tend to use Homebrew more selectively since
relatively, with Homebrew you tend not to have that many packages
installed.
But I have finally got round to doing a proper job of it. Should push
within the month.
Thanks Max. On 1 Aug 2011, at 17:35, Max Howell wrote: >> 2. Why don't I see 'brew upgrade' in the brew manpage ? Is it a 'devel' feature of some sort ? > > Brew upgrade is a hack. I am actually just finishing up the proper command, finally. Cool. > It never got written as people tend to use Homebrew more selectively since relatively, with Homebrew you tend not to have that many packages installed. I imagine that with homebrew becoming more popular with the bleeding edge crowd this will rapidly change. > But I have finally got round to doing a proper job of it. Should push within the month. Out of curiosity, does homebrew keep track of the options specified while installing packages ? I didn't see any brew command that allowed checking the selected options for a specific installed package so am guessing not. If it did, perhaps it would make sense to get 'brew upgrade' to respect these ? I suppose the tricky bits would be to manage conflicts when options change absolutely/semantically etc in the upgraded package version but even alerting the user (and turning this into a human input requirement) would be an efficient compromise. Finally, is there some sort of architectural design description of homebrew (apart from the code of course) ? Cheers, Robin
> Thanks Max. > > On 1 Aug 2011, at 17:35, Max Howell wrote: > >>> 2. Why don't I see 'brew upgrade' in the brew manpage ? Is it a 'devel' feature of some sort ? >> >> Brew upgrade is a hack. I am actually just finishing up the proper command, finally. > > Cool. > >> It never got written as people tend to use Homebrew more selectively since relatively, with Homebrew you tend not to have that many packages installed. > > I imagine that with homebrew becoming more popular with the bleeding edge crowd this will rapidly change. Well we don't install the base that comes with OS X, so maybe not. >> But I have finally got round to doing a proper job of it. Should push within the month. > > Out of curiosity, does homebrew keep track of the options specified while installing packages ? I didn't see any brew command that allowed checking the selected options for a specific installed package so am guessing not. No, this will be a separate bit of work. I think adamv already did some. > If it did, perhaps it would make sense to get 'brew upgrade' to respect these ? I suppose the tricky bits would be to manage conflicts when options change absolutely/semantically etc in the upgraded package version but even alerting the user (and turning this into a human input requirement) would be an efficient compromise. > > Finally, is there some sort of architectural design description of homebrew (apart from the code of course) ? There's some scattered info in the wiki that could use some co-ordination, otherwise the architecture is as simple as it seems, mostly. Max