Pardon the delay, been putting this one off since it's going to be a
fun one to address, and will be a bit long :)
On Thu, Aug 25, 2005 at 12:34:00PM +0200, Paul de Vrieze wrote:
What I mean is compatibility with current portage versions. Current
versions do not understand EAPI. There would
Subject says it all - is there any reason why 3.4.4 installs either
gcc-3.3* or libstdc++-v3 built with gcc-3.3? Is it possible to compile
a native 3.4 system without the old gcc if I don't need binary
compatibility?
--
gentoo-dev@gentoo.org mailing list
Perhaps the init script loader should be changed such that the environment
variables from the shell calling the script are ignored, and an
environment equal to that when being called by init is used.
Definitely. There shouldn't be two different environments depending on
whether a init-script
Don't forget the fact that bash must be execed for normal parses, and
that python has extremely slow string handling when not using one of
the standard parsing modules (that work in C). To put my money where my
mouth is, I've tarred up my code and put it on my dev space:
I have to agree with Flameeyes(diego) on this one. If the switch needs to be
made, no matter what is done. There will be one package that will slip through
and need to be patched. Would be better to get them as we know about them/have
users reporting them. I can think of one or two that should be
On Friday 26 August 2005 09:35, Brian Harring wrote:
Any parser that doesn't support full bash syntax isn't acceptable from
where I sit; re: slow down, 2.1 is around 33% faster sourcing the
whole tree (some cases 60% faster, some 5%, etc). The speed up's are
also what allow template's to be
On Thursday 25 August 2005 21:17, Martin Schlemmer wrote:
On Thu, 2005-08-25 at 13:41 +0200, Paul de Vrieze wrote:
On Wednesday 24 August 2005 15:23, Martin Schlemmer wrote:
Same thing (and probably better option) if you put it in
pkg_setup() ...
Isn't pkg_setup run too when just
On Fri, Aug 26, 2005 at 10:14:04AM +0100, Chris Bainbridge wrote:
Subject says it all - is there any reason why 3.4.4 installs either
gcc-3.3* or libstdc++-v3 built with gcc-3.3?
because i got tired of people complaining about broken systems when they
emerged gcc-3.4.4 and cleaned out all
On Fri, 26 Aug 2005 14:50:52 +0200 Paul de Vrieze [EMAIL PROTECTED]
wrote:
| ps. People please be aware that this is still alpha in the sense of
| not being complete. For better working it should probably support if
| statements properly, and at least do variable substitution. It would
| mean
On Fri, 26 Aug 2005 01:32:11 -0400 Doug Goldstein [EMAIL PROTECTED]
wrote:
| So I know this one has been a sore spot and an annoyance and since I
| don't feel like copying my blog post here I'm just going to link to
| it. I have a solution, one that I know has been brought up before but
| I'm
On Friday 26 August 2005 16:58, Ciaran McCreesh wrote:
On Fri, 26 Aug 2005 14:50:52 +0200 Paul de Vrieze [EMAIL PROTECTED]
wrote:
| ps. People please be aware that this is still alpha in the sense of
| not being complete. For better working it should probably support if
| statements
On Friday 26 August 2005 17:11, Paul de Vrieze wrote:
On Friday 26 August 2005 16:58, Ciaran McCreesh wrote:
On Fri, 26 Aug 2005 14:50:52 +0200 Paul de Vrieze [EMAIL PROTECTED]
wrote:
| ps. People please be aware that this is still alpha in the sense of
| not being complete. For better
On Friday 26 August 2005 16:58, Ciaran McCreesh wrote:
On Fri, 26 Aug 2005 14:50:52 +0200 Paul de Vrieze [EMAIL PROTECTED]
wrote:
| ps. People please be aware that this is still alpha in the sense of
| not being complete. For better working it should probably support if
| statements
On the EAPI subject Brian just brought back, I had this idea that we
could use the same approch XML took with HTML.
The ebuild could define which EAPI to use, but instead beiing a version,
the EAPI would be an ebuild API definition. The equivalent to the XML's
dtd. The ebuild could point to a
Carlos Silva wrote: [Fri Aug 26 2005, 02:18:29PM EDT]
Why was reading the use.local.desc file and noticed that there are 6
packages with this use flag... If nobody oposes it, I'll make it a
global use flag with the Description all the nsplugin local flags
have :)
Please go ahead, this is
On Fri, Aug 26, 2005 at 03:49:35PM -0400, Kristian Benoit wrote:
On the EAPI subject Brian just brought back, I had this idea that we
could use the same approch XML took with HTML.
The ebuild could define which EAPI to use, but instead beiing a version,
the EAPI would be an ebuild API
On Fri, 26 Aug 2005 15:32:42 -0500 Brian Harring [EMAIL PROTECTED]
wrote:
| A) what does xml bring to the table explicitly that is needed?
A cool three letter acronym. Portage is currently lacking in this
department. How are we expected to sell it to enterprise users if it
doesn't use XML?
--
On Fri, 2005-08-26 at 19:18 +0100, Carlos Silva wrote:
Hey!
Why was reading the use.local.desc file and noticed that there are 6
packages with this use flag... If nobody oposes it, I'll make it a
global use flag with the Description all the nsplugin local flags
have :)
Just commited the
Maybe I'm incorrect, but I believe Kristian was not saying use XML,
but using xml as a comparasison (I know there is a better word.. but
its escaping me... that comparassion thing on the SAT's). He's not
saying to use xml, but in order to extend portage, extend it much like
xml extends html, with
Brian Harring [EMAIL PROTECTED] wrote:
On Fri, Aug 26, 2005 at 03:49:35PM -0400, Kristian Benoit wrote:
[snip]
the EAPI would be an ebuild API definition. The equivalent to the XML's
dtd. The ebuild could point to a directory named
$PORTDIR/eapi/eapi-name/ which would contain a python
On Fri, Aug 26, 2005 at 03:02:13PM -0700, Drake Wyrm wrote:
Brian Harring [EMAIL PROTECTED] wrote:
B) EAPI is pretty much bash env template switching
[snip]
Perhaps the EAPI handling could be implemented using eclasses, rather
than something in the deep, dark, python-based internals.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I must say I have been wondering about this for a while too.
A solution might be add some sort of flag to packages that are binary,
and then let portage install libstdc++ the first time you install this
kind of package.
Mike Frysinger skrev:
On Fri,
22 matches
Mail list logo
