On Friday 25 March 2005 03:56 pm, PK wrote: > Esben Mose Hansen wrote: > > On Friday 2005-03-25 18:08, PK wrote: > >>I have found thats its easier to emerge -i file/name when co,ing across > >>a bad package or something then waiting for an update to portage or a > >>new package then re emerging the lot > >> > >>is there a command that lists all injected packages? > > > > I don't know if you can (I suspect no). > > > > But when *I* come across a bad ebuild, I simply mask it: Add it > > to /etc/portage/package.mask > > > > Works a charm, and much easier to manage. > > does nt work for me > I unmerged the inject, added them to a non existent file called > /etc/portage/package.mask and re did the emerge world > zero nada :(
I think what you're talking about is the file you need to create called /etc/portage/profile/package.provided This serves the same pupose as --inject. For example, I added these (among others) to my package.provided file ( I compiled alsa into the kernel, and I don't want emerge to get the others). media-sound/alsa-driver-1.0.8 kde-base/kdegames-3.4.0 kde-base/kdeedu-3.4.0 kde-base/kdetoys-3.4.0 you could also do: >=kde-base/kdegames-3.4.0 to never worry about that package on an emerge -u kde later on. -- [email protected] mailing list
