[gentoo-dev] Re: Calling die in a subshell
Mike Gilbert posted on Mon, 17 Jun 2013 16:49:00 -0400 as excerpted: On 6/17/2013 4:10 PM, viv...@gmail.com wrote: Is it possible to: - keep an open bug (tracker) on named eclasses/ebuilds, so we (users and devs) know that there is a (teoric) fallacy What on earth is a teoric fallacy? My question too. Wictionary and google both appear to agree, however, that while teoric isn't English, it's Catalan (or Aranese/Occitan, the area is NE Spain into south France) for theoretical, which it /is/ close enough sounding/spelling to, to make sense as having the same original root (which wikipedia traces to late Latin from ancient Greek). http://en.wiktionary.org/wiki/te%C3%B2ric -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman
Re: [gentoo-dev] [23]/3 API files
On Sun, Jun 16, 2013 at 02:08:00PM +0200, Alex Legler wrote: - Do you know of more? http://www.gentoo.org/proj/en/metastructure/herds/herds.xml Another one: http://www.gentoo.org/proj/en/devrel/roll-call/userinfo.xml This one and herds are somewhat important, as we really need them to be nicely visible on the website. -- Robin Hugh Johnson Gentoo Linux: Developer, Trustee Infrastructure Lead E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
Re: [gentoo-dev] Re: Calling die in a subshell
On 06/18/13 09:06, Duncan wrote: What on earth is a teoric fallacy? My question too. Wictionary and google both appear to agree, however, that while teoric isn't English, it's Catalan (or Aranese/Occitan, the area is NE Spain into south France) for theoretical, which it /is/ close enough sounding/spelling to, to make sense as having the same original root (which wikipedia traces to late Latin from ancient Greek). http://en.wiktionary.org/wiki/te%C3%B2ric near enough, it was an (unwanted) chimera between Italian and English
Re: [gentoo-portage-dev] [PATCH 0/3] Add cross-prefix support
On 06/17/2013 12:21 AM, Ruud Koolen wrote: This patch series adds support for using a portage installed in one prefix to build packages with a different prefix. The current portage has a single EPREFIX variable specifying both the prefix of the portage installation, and the prefix of the packages portage is building. This patch series splits it into two parts: the portage.const.EPREFIX variable specifying the prefix of the portage installation, used for constructing the PATH as well as the paths to files belonging to a portage installation itself rather than a target root; and the EPREFIX setting in config instances, specifying the prefix of the to-be-built packages and being used for almost everything else. The EPREFIX config setting defaults to const.EPREFIX, but can be overridden by the EPREFIX environment variable, as well as the emerge --prefix option. This allows one to install systems with different prefixes using `EPREFIX=/foo emerge @system`, though some unrelated changes need to happen elsewhere first in order to make that a reality. Ruud Koolen (3): Distinguish between portage prefix and package prefix Based GLOBAL_CONFIG_PATH and DEPCACHE_PATH on portage prefix Pick up EPREFIX environment variable bin/dispatch-conf |2 +- bin/portageq |2 +- pym/_emerge/actions.py |9 + pym/_emerge/main.py|7 pym/portage/_legacy_globals.py |3 +- pym/portage/_sets/__init__.py |3 -- pym/portage/const.py | 34 ++-- pym/portage/dispatch_conf.py |2 +- .../package/ebuild/_config/LocationsManager.py | 22 - pym/portage/package/ebuild/config.py | 21 pym/portage/package/ebuild/doebuild.py |2 +- pym/portage/package/ebuild/fetch.py|4 -- pym/portage/tests/resolver/ResolverPlayground.py |3 +- pym/portage/util/env_update.py |3 +- 14 files changed, 34 insertions(+), 83 deletions(-) I've committed your patches with a few trivial modifications, as noted here: http://bugs.gentoo.org/show_bug.cgi?id=395633#c37 -- Thanks, Zac
