We need to inform the users on how to work with the various /etc/portage files that can be created (and used). These are now the preferred methods, but not really well documented. This includes the files for masking/unmasking/keywords.
Spanky, any progress on this?
I wrote a little guide (only german atm) about the (imo) most useful files in /etc/portage. (http://www.gentoo.de/main/de/portage-2.0.50.xml) Maybe it's an option to translate and integrate this into the handbook?
*bump* joooeeehoeeee, spaaaankyyyyy....
*** Bug 48887 has been marked as a duplicate of this bug. ***
Anybody working on this? I had a look at Tobias guide and think it's worth integrating. This could replace and extend the section about "--upgradeonly" and "ACCEPT_KEYWORDS=~arch". If noone else wants, I can translate it - if someone points me to the handbook's XML source, I can merge it directly.
i have work on my computer to do this and no i havent looked at using Tobias's work because it's based mostly off of the man page i wrote my german isnt great but i can understand most of it ;)
/me is thinking about spanking SpankY...
Did you do it? ;-)
*** Bug 54335 has been marked as a duplicate of this bug. ***
Hey guys. What about simply taking a man page, transforming it into the proper xml, putting it up somewhere and linking to it from doc listing/handbook or whatever? Or even just sayng "read the man page"? I think that'll cover 99% of it. George
Oh, whilw I am at it. Section of this man page: Format: ... does not describe all the choices properly, probably relying on example, which, unfortunately, does not cover everything as well. Example: [skip] # use a package that is marked -* >=sys-kernel/linux-headers-2.6 -* This apparently only covers the explicit "-*". If the package is simply not keyworded for a particular arch you actually have to put "*" there. Well, the intuitivity of such key may be questioned, but this is the one that works.. In any case it may be nice to have the following added to the example. # use a package that is not keyworded for the $ARCH app-foo/bar * George
Um, sorry, the last comment was WRT the package.keywords section of the man page.
Still figuring m way around :). Looks like somehow "~*" may be a better choice at times, as this tends to fetch the latest version, while plain "*" tends to skip versions ?at random? At least both 0.5.1 and 0.6 (of kmymoney2) are lacking any form of amd64 at the moment (and "*" fetched 0.5.1 and "~*" fetched 0.6). The only difference that might have relation here is that 0.5.1 had "x86 ~sparc" and 0.6 had "~x86 ~sparc ~ppc". But why that influences the arch outside of that list at all?? Looks like we might want to ask portage people for some clarification first.. George
I'm assigning back to docs-team@gentoo.org Thomas AW Brown has proposed to update the Gentoo Handbook with this documentation. http://article.gmane.org/gmane.linux.gentoo.documentation/1427 George: the man page is good for references, but not to introduce people to "the Portage way". Just my 2 cents of course
I'd already written up a text file, ready to put onto the Wiki at http://wiki.gentoo-portage.com and realised it would be better offered to the main doc tree. I'll just get to grips with the XML styles used in the docs, and get a proposal up... Tommy.
Using this old bug as it's not closed: just noticed that the handbook still says > In certain cases, an update may mean a downgrade > (i.e. install an older version instead of a newer version). > If you don't want this to happen, use the --upgradeonly option (-U in short): > Code Listing 30: Upgrading your entire system > # emerge --update --upgradeonly world I think it shouldn't look like this. Even the portage docs now state --upgradeonly (-U short option) [...] WARNING: This option is deprecated and shouldn't be used anymore. Please use the /etc/portage/package.* files from now on. At least world should be replaced by a package, even better drop the whole section. Another thing: Just some lines above there is > R (reemerge) The package isn't new, but needs to be reemerged "needs to be reemerged"? I guess that should read "R (replace) ... will be remerged" and maybe explicitly state that there is _no need_ for a remerge.
Actually, just creating the directory /etc/portage and having a few files in it with commented out examples and brief text would help 80 percent of us... base team should be added?
@Aaron: That's what bug #45926 was about... marked as WONTFIX
*** Bug 55207 has been marked as a duplicate of this bug. ***
Updated in the Gentoo Handbook.
Am I too silly to find it or did you forget to commit the changes?
the website isnt updated instantly from cvs, give it a while
The various files of /etc/portage have been integrated in the current text of the second part of the handbook. /etc/portage/package.use has been integrated in the chapter on USE flags (more precisely in "Using USE-flags"). /etc/portage/package.{keywords, unmask, mask} has been integrated in the chapter on "Portage and Software", more precisely in "Working with Masked Packages". /etc/portage/mirrors has been integrated in the chapter on "Controlling Portage Behaviour", more precisely in "Networking Options".
Ok so far, but what about comment #16?
Ah yes, my apologies; I overlooked that one. My fault for assuming a bugreport is about one bug :) I've removed the section on --upgradeonly and changed reemerge with replace.
I should have opened an own bug for it. My main concern is > The package isn't new, but needs to be reemerged which is just a wrong statement. Choose any up-to-date package on your system and run "emerge <pkg> -p" to see what I mean. Anyone who is not too used to portage would have to assume everything on his system "needs to be reemerged".
"emerge <pkg> --pretend" explicitely say "what emerge will reinstall if I reinstall <pkg>?" here, the command line is "emerge --pretend --update <pkg>", and you'll see that there is nothing to upgrade (if pkg is up to date).
The "R" flag will not occur in combination with "--update". Portage does not (yet) have the intelligence to decide whether a package _needs_ to be reemerged. IMHO it makes no sense to list it there.
