-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan wrote:
Nirbheek Chauhan [EMAIL PROTECTED] posted
[EMAIL PROTECTED], excerpted
below, on Sun, 03 Aug 2008 05:37:10 +0530:
How about we just skip the reversed-boolean-usage/it's-a-long-name
confusion/argument and just call it
Nirbheek Chauhan [EMAIL PROTECTED] posted
[EMAIL PROTECTED], excerpted
below, on Sun, 03 Aug 2008 05:37:10 +0530:
How about we just skip the reversed-boolean-usage/it's-a-long-name
confusion/argument and just call it RESTRICT=tarballs ?
I know not all distfiles are tarballs, but it gets the
Zac Medico [EMAIL PROTECTED] posted [EMAIL PROTECTED],
excerpted below, on Sun, 03 Aug 2008 01:57:52 -0700:
I don't like RESTRICT=tarballs because I don't think it's clear enough.
I think we should go with RESTRICT=live-sources. Maybe it doesn't fit
your convention, I'm pretty sure we already
Sorry that this is slightly OT, but maybe one should think
about this point in this discussion:
It seems like USE would be an unconventional location to store that
information and I'm not sure that it really belongs in the ebuild.
USE=live could perfectly make sense, if it is equipped with
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vaeth wrote:
Sorry that this is slightly OT, but maybe one should think
about this point in this discussion:
It seems like USE would be an unconventional location to store that
information and I'm not sure that it really belongs in the ebuild.
Vaeth wrote:
The main point in introducing the live USE flag should be IMHO to
let the user decide whether the sources should be fetched. The fact
that IUSE then marks live ebuilds in the way which you wanted is an
additional side effect.
A tend to agree with Zac that USE flags should not
On Sun, Aug 3, 2008 at 12:25 AM, Zac Medico [EMAIL PROTECTED] wrote:
Santiago M. Mola wrote:
I don't think we're in a hurry for this feature, so I don't see the
need of using suboptimal hacks in order to avoid an EAPI bump.
Furthermore, EAPI 2 is supposed to be done in the near future, right?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe Peterson wrote:
However, I do see the point about the RESTRICT variable. Throwing
random flags into it does not seem ideal, and I think convenience should
take a back seat to correctness when designing, e.g., ebuild
syntax/rules. But why
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zac Medico wrote:
Joe Peterson wrote:
However, I do see the point about the RESTRICT variable. Throwing
random flags into it does not seem ideal, and I think convenience should
take a back seat to correctness when designing, e.g., ebuild
Zac Medico wrote:
What you're missing is that only a specific subset of variables is
cached in /usr/portage/metadata/cache. Now that you mention it, we
could introduce a new variable called EBUILD_FLAGS and start caching
it in new versions of portage. It wouldn't necessarily require an
EAPI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe Peterson wrote:
Yes, that's sort of what I am thinking. Migrate options that really do
not belong in RESTRICT to another variable (and keep them in RESTRICT,
of course, for backward compat for now). Then introduce new ones into
whichever
Zac Medico wrote:
Personally I think people are far too concerned about the name of
the variable. I only see a what I consider to be a trivial or
negligible benefit in separating these things into two different
variables. However, it it makes more people happy then I guess I'm
for it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe Peterson wrote:
I'm not sure the EBUILD_ in EBUILD_FLAGS would be necessary
(redundant?). Maybe even OPTIONS or PROPERTIES makes more sense.
In fact, FLAGS might be a little too generic, even? Worth a short
discussion.
One potential issue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe Peterson wrote:
I'm not sure the EBUILD_ in EBUILD_FLAGS would be necessary
(redundant?). Maybe even OPTIONS or PROPERTIES makes more sense.
In fact, FLAGS might be a little too generic, even? Worth a short
discussion.
I think something
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2008-08-03 23h59 UTC.
Removals:
dev-util/livecd-specs 2008-07-31 00:51:09 wolf31o2
dev-util/livecd-kconfigs2008-07-31 00:57:47 wolf31o2
Hi,
For clarity, I am tomaw, a member of freenode staff. For even more
clarity, I am a member of OFTC staff, although that's not relevant to
this posting. I have spent many hours discussing this issue with
Chrissy and others and feel some points require clarification.
On Fri, 1 Aug 2008
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
As a substitute for the previously discussed RESTRICT=live value[1],
I'd now like you to consider an equivalent PROPERTIES=live-sources
setting. By specifying PROPERTIES=live-sources, an ebuild will be
able to indicate that it uses
17 matches
Mail list logo
