I'd already typed up this response when I saw the one from Alan come in; figured I'd send it anyway - two responses that essentially agree are better than one, right?
On 08/31/2015 02:15 AM, Harry Putnam wrote: > I see there have been a change in how we list our specific use > flags. > > I'm seeing /etc/portage/package.use/ pkg1 pkg2 ... etc rather than > package.use as a file that contains the specific pkgs and use > flags. I'm not certain when it was introduced, but this has been around for a few years now. > I wonder if there is some advantage to leaving things as my > installation has created them or should I revert to the old way > where package.use is file... not a directory. There's no specific advantage to using separate files within a directory to using a single monolithic file other than manageability and some utilities, as far as I'm aware. > If directory is better then how would I list USE flags for > emacs-vcs? <snip> So what is the correct format? Create a file within the package.use directory, named whatever seems reasonable to you, and put the contents: app-editors/emacs-vcs Xaw3d athena gnutls imagemagick toolkit-scroll-bars Enter a single package atom followed by any use flag changes - flag name to enable, minus flag name to disable. In case the above example wrapped, keep the package atom and the flags on a single line. As far as I'm aware, you can't nest files within subdirectories of package.use, and the man page doesn't mention version ranges - it's example is an exact atom (=) and wildcards (see portage(5) man page). -- wraeth <wra...@wraeth.id.au> GnuPG Key: B2D9F759
signature.asc
Description: OpenPGP digital signature
