Closed robhudson closed 14 years ago
It probably helps to know the steps I did leading up to this...
Yesterday (I believe) I installed Git as I saw some updates to both brewkit and git. Today I saw more updates so I did: git pull
, then brew install -f git
.
I tried running it again and got a new error:
/usr/local [git:masterbrew] > brew install -f git ==> Downloading http://kernel.org/pub/software/scm/git/git-1.6.4.2.tar.bz2 File already downloaded and cached ==> ./configure --prefix=/usr/local/Cellar/git/1.6.4.2 ==> make install ==> Downloading http://kernel.org/pub/software/scm/git/git-manpages-1.6.4.2.tar.bz2 File already downloaded and cached ==> Finishing up ln: ./5.10.0: Operation not permitted ==> Error: Could not create symlink /usr/local/lib/perl5/site_perl/5.10.0
Ahh yes this was prolly due to another fix on the site_perl dir. Try brew rm git first. As the force parameter just forces the install, but won't force eg. symlink creation.
Maybe it should though? What do you think?
I removed the pre-existing symlink that was at lib/perl5/site_perl and the install worked.
I think I also misunderstood the brew install -f git
command as something that would update git. The wiki states that an upgrade command doesn't exist yet and it is best to brew rm
and brew install
. Apologies.
If brew install -f package
could be treated like an upgrade, including symlink creation, I think it would be nice. I have mysql installed, for example, and by default the data tables went in /usr/local/Cellar/mysql/5.1.37/var, so brew rm mysql
would also remove the data tables.
I just realized while typing that, though, that this is very not optimal as now my data tables depend on which mysql version is installed. Hmm. I should move those to an appropriate place on my filesystem.
yeah we plan to move the var into Cellar/mysql by default. But I would like more feedback on this as I am not a db user in general so don't know what is best.
I'll leave this open for now because there is a bug in there, but I can't decide which one is the bug and which the feature currently. Time will tell.
I think there may be at least one issue still being described in this thread, but it has drifted away from the bug title.
Might be worth extracting any work items into new bugs and closing this one?
force should force symlink creation as per title.
Just tried brewing something where the targets in bin were already symlinks; "brew install -f" blew away the existing symlinks and created them correctly.
Here's some output of a git build after pulling own that tree:
Also, now that git is broken, I'm not sure of the best way to "git pull" down a fix. :)