[gentoo-portage-dev] Portage color.map settings
Hi! Given the following portage output: troy ~ # USE=examples emerge -pv python --- Invalid atom in /usr/portage/local/layman/dev-zero/profiles/package.mask: =dev-libs/boost-log-scm These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-lang/python-3.1 USE=-build -doc examples* gdbm ipv6 ncurses readline sqlite ssl threads tk -ucs2 -wininst xml 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB troy ~ # The R after [ebuild appears in yellow. The examples (USE-flag) in green. How can I switch those to darker colors? Thanks, Philipp
Re: [gentoo-portage-dev] Portage color.map settings
On Sat, 15 Aug 2009 02:05:05 -0700 Zac Medico zmed...@gentoo.org wrote: With =portage-2.2_rc34, this patch is included: http://bugs.gentoo.org/show_bug.cgi?id=274279 With that you can do things like yellow=darkblue and green=darkgreen. Thanks a lot, this works great. Philipp
Re: [gentoo-portage-dev] Masked by corruption
On 02.01.2007, at 06:56, Zac Medico wrote: In =portage-2.1.2_rc4-r2 t does that now for installed package (see bug #158931). For /var/cache/edb/dep the sqlite module is available (requires pysqlite or python-2.5 with sqlite support enabled). Where can i find documentation about this? I use metadata-transfer at the moment, but all info i got was from the examples-section in man emerge and from the forum. Is there some official complete list of theese modules with some description? Thanks, Philipp -- gentoo-portage-dev@gentoo.org mailing list
Re: [gentoo-portage-dev] Re: Portage phase hooks patch
On Jul 25, 2006, at 9:30 AM, Kevin F. Quinn wrote: If the main issue is cleaning up after an abort, perhaps it would be useful to add a pkg_abort() phase to the package manager; then that can be implemented in an eclass. But i think this could be a problem when FEATURES=keepwork or something like this is enabled. If you create (or Mike creates) a new user, beginns to install files, then maybe there is an error with make test, everything aborts, the new user is deleted. Then someone does FEATURES=-test keepwork emerge dev-foo/bar... you'd have to make shure that the new user gets recreated with the same uid and the group gets recreated with the same gid and if uid or gid are already used in the meantime, then some tricky things have to be done. Or something like this. Philipp, just a user. -- gentoo-portage-dev@gentoo.org mailing list
Re: [gentoo-portage-dev] Re: Re: 2.1 release candidate soon?
On Apr 15, 2006, at 6:10 PM, Duncan wrote: But i really think this is not about helping but about confusion. If i post my emerge --info you don't know if i really use confcache even if i have FEATURES=confcache, because emerge --info does not say if i have emerged confcache and, if i have emerged it, which version it is. I think this should also be listed in emerge --info. Very good point. Should i file a bug on this? Philipp -- gentoo-portage-dev@gentoo.org mailing list
Re: [gentoo-portage-dev] Re: 2.1 release candidate soon?
On Apr 15, 2006, at 8:40 AM, Duncan wrote: Wouldn't the help them out default be consistent with the non-interactive goal for portage? Quit if there's no sane way to go forward without potentially breaking a system, but otherwise, use sane fallbacks where they are possible. I don't think this is about interactive or non-interactive, it's more about strict and non-strict. I think it would be nice to have the you want it but did not emerge it so i don't use it with FEATUERS=- strict and the sorry, not possible, i'll quit with FEATURES=strict. But i really think this is not about helping but about confusion. If i post my emerge --info you don't know if i really use confcache even if i have FEATURES=confcache, because emerge --info does not say if i have emerged confcache and, if i have emerged it, which version it is. I think this should also be listed in emerge --info. Philipp -- gentoo-portage-dev@gentoo.org mailing list
Re: [gentoo-portage-dev] 2.1 release candidate soon?
On Apr 7, 2006, at 5:26 PM, Alec Warner wrote: We have a new cache format, confcache, parallel fetch, etc... The bonus is these features are already mature and relatively old ( a year + as of now ). Reading about confcache i have one question: When i saw, that this feature exists (in make.examples) i activated it. But it did not work because i had not emerged confcache. I think this check should be stricter, if i want confcache and have FEATURES=confcache and confcache is not emerged, i think emerge ... should die, not just say Ok, you said you want it but you don't have it, so i don't use it. What do you think about that? Philipp -- gentoo-portage-dev@gentoo.org mailing list
