You broke the gentoo-x86 by masking these virtuals without the already
converted reverse
dependencies.
Plus I told you to not bother me about this until there is something
broken, or you get
this banned by the PMS, or you get this feature dropped from the PM.
I took the liberty to unbreak the tree
On Fri, 28 Mar 2014 20:02:30 +
Ciaran McCreesh wrote:
> On Fri, 28 Mar 2014 15:46:49 -0400
> Wyatt Epp wrote:
> > On Fri, Mar 28, 2014 at 1:14 PM, Ciaran McCreesh
> > wrote:
> > > On Thu, 27 Mar 2014 03:53:47 +0100
> > > yac wrote:
> > >> What I was describing is the difference between fun
On Wednesday 26 of March 2014 02:07:56 Mike Frysinger wrote:
| cmake is completely broken when it comes to library searching and multilib
and
| cross-compiling. it will happily look in hardcoded / paths to test for the
| existence of files as well as directly execute `pkg-config`. it's a grea
On Monday 24 of March 2014 16:28:44 Ciaran McCreesh wrote:
| On Mon, 24 Mar 2014 10:55:38 -0400
| Damien Levac wrote:
| > A lot of people already replied to this question: package search.
|
| Sure, but can you point to prior examples of this kind of stuff
| actually working?
https://wiki.debian.
On Fri, Mar 28, 2014 at 2:57 PM, Kent Fredric wrote:
>
> On 29 March 2014 06:12, Ciaran McCreesh
> wrote:
>>
>> These look a lot like they're just parameters to an eclass... An
>> alternative approach is to make this explicit, rather than having
>> zillions of environment variables:
>
> inherit p
On Fri, Mar 28, 2014 at 5:48 PM, Rick "Zero_Chaos" Farina
wrote:
> All in all, this isn't a bad idea on the surface, but the first
> arguement shows immediately when this is scaled up. How many other
> packages have multiple libs with different sonames? Off hand, I can
> think of poplar, but I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Recently, without discussion as suggested by the dev manual, new
virtuals were added for libudev and libgudev.
These virtuals are different than any virtuals use in gentoo in the
past, and due to this, I fell the discussion step is critical. As such,
On Fri, Mar 28, 2014 at 4:39 PM, Kent Fredric wrote:
>
> This example for me suggests we'll need to have some kind of process of
> defining what tags should be used for what things, similar to how we have a
> process for global USE, mostly, because inconsistency is a bad thing here.
>
Yes, you wan
And now you file a bug to get that incorrectly applied "terminal" tag
changed to "cli", because they don't mean the same thing.
On Fri, Mar 28, 2014 at 4:06 PM, Kent Fredric wrote:
>
> On 29 March 2014 09:56, yac wrote:
>
>> terminal ∩ jabber ∩ client
>
>
> And now you want *only* terminal ter
On 29 March 2014 09:56, yac wrote:
> terminal ∩ jabber ∩ client
And now you want *only* terminal terminals, do you have to search for
terminal ∩ !( jabber ∪ client ∪ everything ∪ else ) ?
Or
terminal ∩ emulator
( Which may include terminals for emulators instead of terminal emulators )
--
On Sat, 29 Mar 2014 09:39:06 +1300
Kent Fredric wrote:
> On 25 March 2014 03:55, Damien Levac wrote:
>
> > A lot of people already replied to this question: package search.
> >
> > A trivial example, a user want to know all terminals available in
> > portage. Of course he could try a `emerge --
On 25 March 2014 03:55, Damien Levac wrote:
> A lot of people already replied to this question: package search.
>
> A trivial example, a user want to know all terminals available in portage.
> Of course he could try a `emerge --searchdesc terminal`, but then he would
> get anything mentioning ter
On 03/27/2014 18:26, Tom Wijsman wrote:
> On Thu, 27 Mar 2014 13:43:24 +
> "Steven J. Long" wrote:
>> it's still rude of you to constantly quote people's email addresses
>
> Why is it rude? There are a lot of other developers on the list here
> that do this as well; so, if you want to see this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ciaran McCreesh:
> On Fri, 28 Mar 2014 15:46:49 -0400 Wyatt Epp
> wrote:
>> On Fri, Mar 28, 2014 at 1:14 PM, Ciaran McCreesh
>> wrote:
>>> On Thu, 27 Mar 2014 03:53:47 +0100 yac wrote:
What I was describing is the difference between fundamen
On Fri, 28 Mar 2014 15:46:49 -0400
Wyatt Epp wrote:
> On Fri, Mar 28, 2014 at 1:14 PM, Ciaran McCreesh
> wrote:
> > On Thu, 27 Mar 2014 03:53:47 +0100
> > yac wrote:
> >> What I was describing is the difference between fundamental
> >> properties of categories and tags.
> >
> > You are trying to
On Fri, Mar 28, 2014 at 1:14 PM, Ciaran McCreesh
wrote:
> On Thu, 27 Mar 2014 03:53:47 +0100
> yac wrote:
>> What I was describing is the difference between fundamental properties
>> of categories and tags.
>
> You are trying to redefine categories in terms of a concept that they
> didn't origina
On 29 March 2014 06:12, Ciaran McCreesh wrote:
> These look a lot like they're just parameters to an eclass... An
> alternative approach is to make this explicit, rather than having
> zillions of environment variables:
>
Something I'd *like* to be able to do is have eclass specific keys that map
I picked up maintenance for net-misc/openswan a coupe of years ago.
The project has since been forked by its main maintainer upstream into
the "libreswan" project. This seems to be better maintained than the
current openswan software. I have added libreswan to the tree and it
is what I use on a da
On Fri, Mar 28, 2014 at 10:12 AM, Ciaran McCreesh <
ciaran.mccre...@googlemail.com> wrote:
> On Sat, 29 Mar 2014 01:44:06 +1300
> Kent Fredric wrote:
> > On 28 March 2014 23:47, Michał Górny wrote:
> > > Please paste a real example, it's easier to understand what you're
> > > trying to do when w
On Thu, 27 Mar 2014 03:53:47 +0100
yac wrote:
> What I was describing is the difference between fundamental properties
> of categories and tags.
You are trying to redefine categories in terms of a concept that they
didn't originally represent. From a package mangler perspective,
categories aren't
On Sat, 29 Mar 2014 01:44:06 +1300
Kent Fredric wrote:
> On 28 March 2014 23:47, Michał Górny wrote:
> > Please paste a real example, it's easier to understand what you're
> > trying to do when we see what it does.
>
>
> For the A.1 style:
>
> MODULE_AUTHOR=DOY
> MODULE_VERSION=2.0604
> inheri
On 28 March 2014 23:47, Michał Górny wrote:
> Please paste a real example, it's easier to understand what you're
> trying to do when we see what it does.
>
For the A.1 style:
MODULE_AUTHOR=DOY
MODULE_VERSION=2.0604
inherit perl-module
^ from Moose 2.60.400.ebuild , this creates SRC_URI based
Dnia 2014-03-28, o godz. 20:11:47
Kent Fredric napisał(a):
> I often see one of two patterns:
Please paste a real example, it's easier to understand what you're
trying to do when we see what it does.
--
Best regards,
Michał Górny
signature.asc
Description: PGP signature
On Fri, 28 Mar 2014 20:11:47 +1300
Kent Fredric wrote:
> What I keep wanting to have is a hook that triggers after the ebuild
> is loaded, defined in the eclass.
+1 Yes, please.
My habit is to follow A.1 unless I know of the functionality that B.1
would assume, in which case I would put things
I often see one of two patterns:
Pattern A) Code Before `inherit` to drive behaviour
Example A.1
SOME_VALUE="Foo"
inherit someclass
OTHERVALUE=Bar"
inherit someotherclass
This is used heavily in things using perl-module.eclass
Pattern B) Require either function calls or have a finalising fun
25 matches
Mail list logo
