[gentoo-user] Re: libxml2 conflicts

[»Q«]

On Wed, 13 Jan 2016 17:01:47 +
Neil Bothwick  wrote:

> I use a directory for package.use, then autounmask puts its entries in
> the last file in there, so I have a file called zzz-autounmask. It's
> pretty easy to clean up, just delete/move it and run emerge -u @world
> again and it will be repopulated with any settings that are still
> needed.

Thanks for that.  I haven't been using autounmask, partly because I
didn't think it could handle package.* a directories.  (Maybe I was
wrong all along or maybe when autounmask debuted I was right;  doesn't
matter now.)



  

Re: [gentoo-user] Re: libxml2 conflicts

[Neil Bothwick]

On Wed, 13 Jan 2016 12:51:07 -0600, »Q« wrote:

> > I use a directory for package.use, then autounmask puts its entries in
> > the last file in there, so I have a file called zzz-autounmask. It's
> > pretty easy to clean up, just delete/move it and run emerge -u @world
> > again and it will be repopulated with any settings that are still
> > needed.  
> 
> Thanks for that.  I haven't been using autounmask, partly because I
> didn't think it could handle package.* a directories.  (Maybe I was
> wrong all along or maybe when autounmask debuted I was right;  doesn't
> matter now.)

Directories have always worked with automask because portage translates
the contents to a single file anyway. The only thng you have to be
careful of is file naming, because automask always adds ot the end of
package.use, which means it modifies the last file.


-- 
Neil Bothwick

If you can't be kind, be vague.


pgpJDdc_qUPfw.pgp
Description: OpenPGP digital signature

[gentoo-user] Re: libxml2 conflicts

[James]

Neil Bothwick  digimed.co.uk> writes:


> I use a directory for package.use, then autounmask puts its entries in
> the last file in there, so I have a file called zzz-autounmask. It's
> pretty easy to clean up, just delete/move it and run emerge -u   world
> again and it will be repopulated with any settings that are still needed.


OK, I'll give this a spin. One questions, where to move/name the traditional
flag settings I have in the top of the old file, here are a few for clarity::

media-sound/hydrogenportaudio
dev-util/valgrind   mpi
net-irc/quassel webkit
app-portage/layman  sync-plugin-portage  subversion  
net-wireless/kismet -bluetooth
net-libs/libpcap-bluetooth
sci-libs/hdf5   -cxx examples -fortran threads zlib mpi


Two file, zzz-autounmaks for it's entris and just place those above in this
file::/etc/portage/package.use/package.use?

And both  get properly parsed by emerge updates? 


James

Re: [gentoo-user] Re: libxml2 conflicts

[Neil Bothwick]

On Wed, 13 Jan 2016 17:24:21 + (UTC), James wrote:

> > I use a directory for package.use, then autounmask puts its entries in
> > the last file in there, so I have a file called zzz-autounmask. It's
> > pretty easy to clean up, just delete/move it and run emerge -u  
> > world again and it will be repopulated with any settings that are
> > still needed.  
> 
> 
> OK, I'll give this a spin. One questions, where to move/name the
> traditional flag settings I have in the top of the old file, here are a
> few for clarity::
> 
> media-sound/hydrogenportaudio
> dev-util/valgrind   mpi
> net-irc/quassel webkit
> app-portage/layman  sync-plugin-portage  subversion  
> net-wireless/kismet -bluetooth
> net-libs/libpcap-bluetooth
> sci-libs/hdf5   -cxx examples -fortran threads zlib mpi
> 
> 
> Two file, zzz-autounmaks for it's entris and just place those above in
> this file::/etc/portage/package.use/package.use?
> 
> And both  get properly parsed by emerge updates? 
> 
Exactly. When package.* is a directory, portage treats all of its
contents as a single file, in lexical order. Look at the description
for /etc/portage/ in the portage man page.


-- 
Neil Bothwick

Accordion: a bagpipe with pleats.


pgp47giZTf4Wv.pgp
Description: OpenPGP digital signature