View previous topic :: View next topic |
Author |
Message |
Tuna Guru
Joined: 19 Jul 2002 Posts: 485 Location: Berlin
|
Posted: Tue Oct 01, 2002 1:51 pm Post subject: gentoo, portage and USE |
|
|
hi i was wondering about something..
poke me if it is in the guides and i havnt noticed.
for example.. i have some common USE flags in my make.conf so i feel comfortable with my system. but know i decided to have program x (e.g. apache) and of course i dont want to change my system wide USE flags if i want to support berkleydb in mod_php. so i do a
Code: | export USE="mod_php berkleydb" |
this is an example so dont punch me if there are some typing mistake. now after everyhting went fine (as always) everything is nice and i can open up my next can of beer. but now something terrible happens.. program x has a bug.. and some evil nerd made an ebuild 20 minutes after the fix and i really want to update as soon as possible. now the question:
what iis the appropiate way to upgrade the package?
Code: | emerge rsync
emerge x
emerge clean |
or
Code: | emerge rsync
emerge -u x |
and (this is the important part) what happens to the custom USE flags i entered while first installing the program? are they stored somewhere and reused? or do i have to figure it out again what i want to use?
would be nice if someone can clearify this a bit, thx. |
|
Back to top |
|
|
garo Bodhisattva
Joined: 15 Jul 2002 Posts: 860 Location: Edegem,BELGIUM
|
Posted: Tue Oct 01, 2002 2:03 pm Post subject: |
|
|
Code: | emerge rsync && emerge -C x && emerge x |
is the safe way
Code: | emerge rsync && emerge -u x |
is the fast way |
|
Back to top |
|
|
BackSeat Apprentice
Joined: 12 Apr 2002 Posts: 242 Location: Reading, UK
|
Posted: Tue Oct 01, 2002 2:07 pm Post subject: |
|
|
To answer your question: the custom USE flags are lost. Why don't you simply set the USE statement in /etc/make.conf to be what you want?
BS |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Tue Oct 01, 2002 2:52 pm Post subject: |
|
|
When there is a package being updated for security reasons, the announcements recommend: Code: | emerge rsync
emerge some-package
emerge clean |
_________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
Tuna Guru
Joined: 19 Jul 2002 Posts: 485 Location: Berlin
|
Posted: Tue Oct 01, 2002 4:26 pm Post subject: |
|
|
well yeah.. i could do them in make.conf.. but i dont want to..
i may want to compile a program with qt support for example but others not.. and changing make.conf all the time is a pain in *$%&%. !
and put 'berkleydb' into make.conf for just a special exception just doesnt seem right..
are we really lacking some flexibillity here?! |
|
Back to top |
|
|
thegarbageman n00b
Joined: 28 Apr 2002 Posts: 74 Location: Overland Park, KS
|
Posted: Tue Oct 01, 2002 4:38 pm Post subject: |
|
|
Perhaps this comment has been previously made, but would it not be great to be able to "pin" use flags to a package, similar to the way one might pin a specific version? |
|
Back to top |
|
|
justus n00b
Joined: 16 Apr 2002 Posts: 48
|
Posted: Fri Oct 04, 2002 9:49 am Post subject: Hmmm... |
|
|
Heya...
I think that this is already available... I am not exactly sure how this works as I have not tried it, however I would assume that on a clean install of the program (ie. emerge kdelibs) it would use your normal flags. On an update (emerge -u kdelibs) it would use the flags that it was previously installed with.
These flags themselves are recorded with every installed program in:
Code: | /var/db/pkg/pkg-tree/pkg-name |
So the information is recorded there.
As for the other...Another option, instead of exporting, is to do something like:
Code: | # USE="-gnome kde" emerge whatever |
This is something that I have done in the past and it works like a charm. Basically does the same thing as exporting, but only for the command that follows.
Hope that helps,
Justin T |
|
Back to top |
|
|
|