> Sorry, but this mailing list is not really the best place for "just for
> fun" bash foo. I suggest you take it somewhere else.
Actually that was a question which whitespaces are allowed in IUSE, so I think
it's not the worst place for it. Especially if you count the number of flame
senseless po
Piotr Jaroszyński wrote:
> Just for fun(=I wouldn't use it in ebuild/eclass):
Sorry, but this mailing list is not really the best place for "just for
fun" bash foo. I suggest you take it somewhere else.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing lis
> And this is the point: Your definition of 'works' is (in my eyes) at
> least sloppy. If it doesn't work for all sensible cases, it shouldn't
> be labelled as 'works'.
Does "dirty portage-specific hack" mean "That's my bulletproof solution for
that problem"? I didn't mean that and I hope that's o
Am Montag, 30. Oktober 2006 22:19 schrieb Piotr Jaroszyński:
> > Whitespace. Not space.
> >
> > E_IUSE=$'foo\tX'
>
> Ok, you are right here. Sorry for saying that you don't know what you
> are talking about, it seems you do. But don't assume that everyone
> else don't. And for future you could be m
> Whitespace. Not space.
>
> E_IUSE=$'foo\tX'
Ok, you are right here. Sorry for saying that you don't know what you are
talking about, it seems you do. But don't assume that everyone else don't.
And for future you could be more specific, "Doesn't work", esp. If something
do work(not the right wa
Hello Piotr
On Mon, Oct 30, 2006 at 09:40:28PM +0100, Piotr Jaroszyński wrote:
> E_IUSE=${E_IUSE// X } - deletes every X with whitespace around it.
What happens if someone uses newlines, horizontal tabs, vertical tabs or
any other whitespace character instead of spaces? Boom.
Greets,
Michael
--
> E_IUSE=${E_IUSE// X } - deletes every X with whitespace around it.
This should be E_IUSE=${E_IUSE// X / }.
--
Piotr Jaroszyński
Gentoo Developer
--
gentoo-dev@gentoo.org mailing list
On Mon, 30 Oct 2006 21:30:56 +0100 Piotr Jaroszyński <[EMAIL PROTECTED]>
wrote:
| Why there is always *someone* who wants to win a pink elephant in the
| last word contest?
We want to be damned sure that neither you nor anyone else is going to
persist with this kind of stupidity.
--
Ciaran McCre
> | > Just what do you think will happen when another eclass sets
> | > IUSE="Xaw3d"?
> |
> | Specially for you and your pink elephants:
> | E_IUSE=${E_IUSE// X }
> | E_IUSE=${E_IUSE#X }
> | E_IUSE=${E_IUSE% X}
>
> No go. Arbitrary whitespace is allowed.
I thought that you really know what you are
> ...yet. Past Portage releases don't have it. Future Portage releases may
> not. Other package managers don't. Using it at all is to intentionally
> screw around with things that ebuilds should not know or need to, is
> asking for trouble, and will have a certain group on your back as soon
> as th
On Mon, 30 Oct 2006 21:04:47 +0100 Piotr Jaroszyński <[EMAIL PROTECTED]>
wrote:
| > Yes, I do want to bet. You don't have a clue what you're talking
| > about and you don't have a clue how to use bash substitution
| > correctly.
|
| Have you bet that you won't be kicked from gentoo also?
Oh, I thi
On Mon, 30 Oct 2006 21:04:47 +0100
Piotr Jaroszyński <[EMAIL PROTECTED]> wrote:
> > Just what do you think will happen when Portage internals change?
> > This has happened several times with those variables?
> E_IUSE was added in 2.0.50-r10 or r11 and was never changed.
...yet. Past Portage relea
Ciaran McCreesh wrote:
Your solution is approximately on par with fixing a wobbly chair by
sawing off all four legs and then attaching what's left to a crocodile.
+1 for creativity and making me literally laugh out loud
--
Andrew Gaffneyhttp://dev.gentoo.org/~agaffn
On Mon, 30 Oct 2006 19:21:46 +0100 Piotr Jaroszyński <[EMAIL PROTECTED]>
wrote:
| > And it doesn't work.
|
| Wanna bet? Of course you must put it in the x-modular.eclass, but I
| thought that's quite obvious as spyderous was talking about adding
| IUSE="" to that eclass.
Yes, I do want to bet. You
Diego 'Flameeyes' Pettenò wrote:
> On Monday 30 October 2006 17:26, Donnie Berkholz wrote:
>> Anyone got any ideas? The only one I have is to add significant missing
>> functionality to font.eclass and switch every font package over that
>> instead of x-modular.eclass.
>
> if [[ ${CATEGORY} == "me
> And it doesn't work.
Wanna bet? Of course you must put it in the x-modular.eclass, but I thought
that's quite obvious as spyderous was talking about adding IUSE="" to that
eclass.
--
Piotr Jaroszyński
Gentoo Developer
--
gentoo-dev@gentoo.org mailing list
On Mon, 30 Oct 2006 18:44:30 +0100 Piotr Jaroszyński <[EMAIL PROTECTED]>
wrote:
| > I really want to use font.eclass in x-modular.eclass to get rid of
| > a lot of code duplication and more possible bugs. Problem is, it
| > brings in IUSE=X for every single X package. I cannot figure out
| > how to
> I really want to use font.eclass in x-modular.eclass to get rid of a lot
> of code duplication and more possible bugs. Problem is, it brings in
> IUSE=X for every single X package. I cannot figure out how to prevent
> this. Setting IUSE="" after the inherit in x-modular.eclass is not enough.
E_IU
On Monday 30 October 2006 17:26, Donnie Berkholz wrote:
> Anyone got any ideas? The only one I have is to add significant missing
> functionality to font.eclass and switch every font package over that
> instead of x-modular.eclass.
if [[ ${CATEGORY} == "media-font" ]]; then
fonteclass="font"
end
On Mon, 2006-30-10 at 08:26 -0800, Donnie Berkholz wrote:
> Alternate subject: On the sudden appearance of USE=X for tons of stuff
>
> I really want to use font.eclass in x-modular.eclass to get rid of a lot
> of code duplication and more possible bugs. Problem is, it brings in
> IUSE=X for every
Alternate subject: On the sudden appearance of USE=X for tons of stuff
I really want to use font.eclass in x-modular.eclass to get rid of a lot
of code duplication and more possible bugs. Problem is, it brings in
IUSE=X for every single X package. I cannot figure out how to prevent
this. Setting I
21 matches
Mail list logo
