On Mon, 15 Apr 2013 10:56:45 +
"Aaron W. Swenson" wrote:
> ROOT being a user set variable, having ROOT be an empty string by
> default still does not guarantee that ROOT won't end with a
> slash. Even if we change it so that it defaults to an empty string, it
> won't negate the need to do ${RO
On Sun, Apr 14, 2013 at 06:59:19PM +0200, Michał Górny wrote:
> On Sun, 14 Apr 2013 17:39:44 +0100
> Ciaran McCreesh wrote:
>
> > On Sun, 14 Apr 2013 16:58:07 +0200
> > Michał Górny wrote:
> > > On Sun, 14 Apr 2013 15:22:42 +0100
> > > Ciaran McCreesh wrote:
> > > > On Sat, 13 Apr 2013 23:23:57
On Sun, 14 Apr 2013 17:39:44 +0100
Ciaran McCreesh wrote:
> On Sun, 14 Apr 2013 16:58:07 +0200
> Michał Górny wrote:
> > On Sun, 14 Apr 2013 15:22:42 +0100
> > Ciaran McCreesh wrote:
> > > On Sat, 13 Apr 2013 23:23:57 +0200
> > > Michał Górny wrote:
> > > > As most of you probably doesn't know
On Sun, 14 Apr 2013 16:58:07 +0200
Michał Górny wrote:
> On Sun, 14 Apr 2013 15:22:42 +0100
> Ciaran McCreesh wrote:
> > On Sat, 13 Apr 2013 23:23:57 +0200
> > Michał Górny wrote:
> > > As most of you probably doesn't know, PMS guarantees that ${D}
> > > always ends with a slash. It seems that t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sun, 14 Apr 2013 16:14:57 +0200
hasufell wrote:
> On 04/13/2013 11:23 PM, Michał Górny wrote:
> > Your thoughts?
> >
>
> Sounds ok, but how will the transition happen exactly? Will the
> behavior just change for new EAPIs or for all? If for al
On Sun, 14 Apr 2013 15:22:42 +0100
Ciaran McCreesh wrote:
> On Sat, 13 Apr 2013 23:23:57 +0200
> Michał Górny wrote:
> > As most of you probably doesn't know, PMS guarantees that ${D} always
> > ends with a slash. It seems that this particular wording was enforced
> > by historical portage behav
On Sat, 13 Apr 2013 23:23:57 +0200
Michał Górny wrote:
> As most of you probably doesn't know, PMS guarantees that ${D} always
> ends with a slash. It seems that this particular wording was enforced
> by historical portage behavior (instead of fixing the ebuilds...) yet
> it didn't ever get really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/13/2013 11:23 PM, Michał Górny wrote:
> Your thoughts?
>
Sounds ok, but how will the transition happen exactly? Will the
behavior just change for new EAPIs or for all? If for all, who will do
the tinderbox run?
-BEGIN PGP SIGNATURE-
Ver
On Sun, 14 Apr 2013 13:32:29 +0200
Michał Górny wrote:
> There you can find at least my rough estimates of how many ebuilds
> are directly affected. Shortly saying, if we fix PMS, we need to fix,
> say, 200 ebuilds. If we leave it as is, we have around 1750 obviously
> broken ebuilds + over 3000
On Sat, 13 Apr 2013 23:23:57 +0200
Michał Górny wrote:
> As most of you probably doesn't know, PMS guarantees that ${D} always
> ends with a slash. It seems that this particular wording was enforced
> by historical portage behavior (instead of fixing the ebuilds...) yet
> it didn't ever get reall
Michał Górny wrote:
> Your thoughts?
+1
pgp1yo32f0xoD.pgp
Description: PGP signature
On 4/13/2013 2:23 PM, Michał Górny wrote:
Your thoughts?
+1, this causes untold agonies for my pet platform. See #465772 for
more thorough griping :)
-gmt
Hello,
As most of you probably doesn't know, PMS guarantees that ${D} always
ends with a slash. It seems that this particular wording was enforced
by historical portage behavior (instead of fixing the ebuilds...) yet
it didn't ever get really widespread.
Specifically, it is awfully counter-intuit
13 matches
Mail list logo
