-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan wrote:
> Zac Medico <[EMAIL PROTECTED]> posted [EMAIL PROTECTED],
> excerpted below, on Sun, 28 Sep 2008 15:56:27 -0700:
>
>> For example, `emerge kde-meta` would behave as as normal meta-package
>> currently does, and `emerge @kde-meta` would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rémi Cardona wrote:
> Zac Medico a écrit :
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi everyone,
>>
>> Please consider a PROPERTIES=set value that allows an ebuild to
>> indicate that it should behave like a package set when selected o
Zac Medico a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
Please consider a PROPERTIES=set value that allows an ebuild to
indicate that it should behave like a package set when selected on
the command line. This is behavior is somewhat difficult to describe
in words but th
On Sat, Sep 27, 2008 at 3:47 PM, Thomas Sachau <[EMAIL PROTECTED]> wrote:
> So what about this one?
>
> default_src_install() {
>if [ -f Makefile ] || [ -f GNUmakefile ] || [ -f makefile ]; then
>emake DESTDIR="${D}" install || die "emake install failed"
>fi
>
Zac Medico <[EMAIL PROTECTED]> posted [EMAIL PROTECTED],
excerpted below, on Sun, 28 Sep 2008 15:56:27 -0700:
> For example, `emerge kde-meta` would behave as as normal meta-package
> currently does, and `emerge @kde-meta` would reference the same package
> as a set and could thereby trigger diff
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2008-09-28 23h59 UTC.
Removals:
sci-libs/blas-config2008-09-23 10:27:32 bicatali
sci-libs/lapack-config 2008-09-23 10:28:05 bicatali
sci-libs/libsc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Sun, 28 Sep 2008 15:56:27 -0700
> Zac Medico <[EMAIL PROTECTED]> wrote:
>> As I've tried to explain, the an ebuild which exhibits
>> PROPERTIES=set doesn't necessarily have to behave any differently
>> than a meta-package cu
On Sun, 28 Sep 2008 15:56:27 -0700
Zac Medico <[EMAIL PROTECTED]> wrote:
> As I've tried to explain, the an ebuild which exhibits
> PROPERTIES=set doesn't necessarily have to behave any differently
> than a meta-package currently does. What we would do is create a
> configuration that maps the set-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Sun, 28 Sep 2008 15:11:42 -0700
> Zac Medico <[EMAIL PROTECTED]> wrote:
>>> GLEP 37 effectively abolishes virtuals. It doesn't try to overload
>>> new behaviour onto packages.
>> Well, PROPERTIES=set doesn't necessarily need
On Sun, 28 Sep 2008 15:11:42 -0700
Zac Medico <[EMAIL PROTECTED]> wrote:
> > GLEP 37 effectively abolishes virtuals. It doesn't try to overload
> > new behaviour onto packages.
>
> Well, PROPERTIES=set doesn't necessarily need overload new behavior
> onto packages any more that virtual ebuilds do.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Sun, 28 Sep 2008 13:53:12 -0700
> Zac Medico <[EMAIL PROTECTED]> wrote:
Does this seem like a good approach? Are there any suggestions for
improvements or alternative approaches?
>>> Strikes me as a good way of cau
On Sun, 28 Sep 2008 13:53:12 -0700
Zac Medico <[EMAIL PROTECTED]> wrote:
> >> Does this seem like a good approach? Are there any suggestions for
> >> improvements or alternative approaches?
> >
> > Strikes me as a good way of causing extreme confusion for users...
>
> Perhaps it's not so confusin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Sat, 27 Sep 2008 17:21:18 -0700
> Zac Medico <[EMAIL PROTECTED]> wrote:
>> Does this seem like a good approach? Are there any suggestions for
>> improvements or alternative approaches?
>
> Strikes me as a good way of causin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ciaran McCreesh wrote:
> On Sun, 28 Sep 2008 10:42:39 -0700
> Zac Medico <[EMAIL PROTECTED]> wrote:
>> Some some sort of mapping of packages into sets space does seem
>> better than changing the behavior of these packages other cases.
>> However, PROPE
On Sat, 27 Sep 2008 17:21:18 -0700
Zac Medico <[EMAIL PROTECTED]> wrote:
> Does this seem like a good approach? Are there any suggestions for
> improvements or alternative approaches?
Strikes me as a good way of causing extreme confusion for users...
Consider sets in package.use, for example. Any
Donnie Berkholz wrote:
- All our docs should be updated to refer to irc.gentoo.org instead of
irc.freenode.net.
Fixed in irc.xml and most of our other documentation in /doc/en/; will
fix the rest later.
signature.asc
Description: OpenPGP digital signature
On Sun, 28 Sep 2008 10:42:39 -0700
Zac Medico <[EMAIL PROTECTED]> wrote:
> Some some sort of mapping of packages into sets space does seem
> better than changing the behavior of these packages other cases.
> However, PROPERTIES=set will still be useful for governing
> recursion, since recursion int
Hi all,
I just posted the summaries from August & September meetings. The
complete summaries & logs are at http://www.gentoo.org/proj/en/council/.
Here's the most important bits:
- EAPI=2 is approved for use in the tree. P
Thomas Sachau wrote:
> I see many ebuild that still use "econf || die", also econf should die by
> itself. Are there any
> specific reasons for this? Some cases where econf does not die also it fails?
> Or some other reason
> for this?
My guess is that due to the general lack of consistency in w
I see many ebuild that still use "econf || die", also econf should die by
itself. Are there any
specific reasons for this? Some cases where econf does not die also it fails?
Or some other reason
for this?
Some feedback on this would be nice.
Thanks
--
Thomas Sachau
Gentoo Linux Developer
s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Mauch wrote:
> On Sat, 27 Sep 2008 17:21:18 -0700
> Zac Medico <[EMAIL PROTECTED]> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi everyone,
>>
>> Please consider a PROPERTIES=set value that allows an ebuild to
>> indicate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Donnie Berkholz wrote:
> On 09:19 Wed 17 Sep , Zac Medico wrote:
>> I suggest that we unmask the appropriate ARCH flags in
>> profiles/arch/*/use.mask, add ../base to profiles/arch/*/parent, and
>> create profiles/arch/base/use.mask to mask all of
On 09:19 Wed 17 Sep , Zac Medico wrote:
> I suggest that we unmask the appropriate ARCH flags in
> profiles/arch/*/use.mask, add ../base to profiles/arch/*/parent, and
> create profiles/arch/base/use.mask to mask all of the existing ARCH
> flags. This will serve to mask all but the appropriate
On Sat, 27 Sep 2008 17:21:18 -0700
Zac Medico <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi everyone,
>
> Please consider a PROPERTIES=set value that allows an ebuild to
> indicate that it should behave like a package set when selected on
> the command line.
24 matches
Mail list logo
