It turns out that /etc/portage/package.keywords and /etc/portage/package.unmask can be directories, which is convenient for organizational purposes. If this is the case, autounmask does the smart thing and creates the file autounmask-pkgname (in this case, autounmask-kde-meta) in those folders. I find this a much easier way to try it out, and maintain its additions. On Sun, 2008-10-05 at 17:30 -0500, Dale wrote: > Neil Bothwick wrote: > > > > It basically adds a bunch of packages to /etc/portage/packages.unmask > > and /etc/portage/packages.keywords, bracketed by start/end comments so > > you can remove them. It's a quick and easy way of emerging something > > with a lot of masked dependencies, like kde-meta:4. > > > > I used it the last time I tried KDE4 and it did just as was expected, > > except is added =cat/pkg-vers, which I changed to ~cat/pkg/vers so I > > could pick up and fixes. > > > > > > > > You can tell it not to put versions tho. > > [EMAIL PROTECTED] / # autounmask -h > > autounmask version 0.21 (using PortageXS-0.02.07 and portage-2.2_rc11) > > Usage: > autounmask category/package-version > > Options: > -h, --help : Show this help. > -p, --pretend : Just pretend. > -n, --noversions : Do not append version when unmasking a > package. <<<<-------------- > > [EMAIL PROTECTED] / # > > Just use the -n option. I haven't used that that I can recall tho. Now > watch some guru come up with a script to remove them. ;-) > > Dale > > :-) :-) >
signature.asc
Description: This is a digitally signed message part
