> On Thu, 3 Aug 2017, Michael Orlitzky wrote:
> On 08/03/2017 06:33 PM, Ulrich Mueller wrote:
>> It did, even back in 2004:
>> https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-guide-ebuild.xml?hideattic=0&revision=1.10&view=markup#l534
> You got me, b
On czw, 2017-08-03 at 23:24 -0400, Michael Orlitzky wrote:
> On 08/03/2017 06:33 PM, Ulrich Mueller wrote:
> > > > > > > On Thu, 3 Aug 2017, Michael Orlitzky wrote:
> > > The developer handbook that I just said didn't mention variables in
> > > HOMEPAGE at all.
> >
> > It did, even back in 2004:
>
On 08/03/2017 06:33 PM, Ulrich Mueller wrote:
>> On Thu, 3 Aug 2017, Michael Orlitzky wrote:
>
>> The developer handbook that I just said didn't mention variables in
>> HOMEPAGE at all.
>
> It did, even back in 2004:
> https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/proj/en/de
On Thu, Aug 03, 2017 at 05:54:17PM +0200, Michał Górny wrote:
> d. no random ${PN} all over the install phase.
I think some qualification of "random ${PN} all over the install phase"
needs to be made - how random is random, are there any allowed
instances?
AFAIK with the exception of some system-
> On Thu, 3 Aug 2017, Michael Orlitzky wrote:
> On 08/03/2017 03:39 PM, Mike Gilbert wrote:
>> The developer handbook was also a "policy" manual of sorts when it
>> existed.
> The developer handbook that I just said didn't mention variables in
> HOMEPAGE at all.
It did, even back in 2004:
ht
On Thu, Aug 3, 2017 at 11:54 AM, Michał Górny wrote:
> On czw, 2017-08-03 at 11:33 -0400, Mike Gilbert wrote:
>> I would like to remove the ban on variable references in the HOMEPAGE
>> variable in ebuilds.
>>
>> As I understand it, this ban was put in place so that people can
>> easily copy/paste
On Thu, Aug 3, 2017 at 3:56 PM, Michael Orlitzky wrote:
> On 08/03/2017 03:39 PM, Mike Gilbert wrote:
>>>
>>> (The old handbook never mentioned variables, from what I can see.)
>>>
>>
>> The developer handbook was also a "policy" manual of sorts when it existed.
>
> The developer handbook that I j
# Michał Górny (04 Aug 2017)
# Obsolete. Replaced by media-gfx/graphite2. No longer used
# by anything. Removal in 30 days. Bug #594314.
media-libs/silgraphite
# Michał Górny (04 Aug 2017)
# Dependency of dev-texlive/texlive-basic-2012 no longer needed for
# the current versions. Removal in 14 d
On 08/03/2017 03:39 PM, Mike Gilbert wrote:
>>
>> (The old handbook never mentioned variables, from what I can see.)
>>
>
> The developer handbook was also a "policy" manual of sorts when it existed.
The developer handbook that I just said didn't mention variables in
HOMEPAGE at all.
On Thu, Aug 3, 2017 at 3:12 PM, Michael Orlitzky wrote:
> On 08/03/2017 02:57 PM, Mike Gilbert wrote:
>>
>> It's in the devmanual, which imposes gentoo-specific policy on top of PMS.
>>
>
> It would be nice if that were true, but there's a lot of junk and/or
> personal preference documented in the
> On Thu, 3 Aug 2017, Michael Orlitzky wrote:
> [...] Portage Manager Specification [...]
D'oh!
pgp6Uct6pop5G.pgp
Description: PGP signature
> On Thu, 3 Aug 2017, Mike Gilbert wrote:
> I would like to remove the ban on variable references in the
> HOMEPAGE variable in ebuilds.
I think this is not a good idea. For example, it would break
browse-url-at-point (C-u u .) from within Emacs.
> [...]
> Allowing variables in HOMEPAGE wou
On 08/03/2017 02:57 PM, Mike Gilbert wrote:
>
> It's in the devmanual, which imposes gentoo-specific policy on top of PMS.
>
It would be nice if that were true, but there's a lot of junk and/or
personal preference documented in the devmanual, and a lot of
actual-policy that's still missing becau
On Thu, Aug 3, 2017 at 2:21 PM, Michael Orlitzky wrote:
> On 08/03/2017 11:33 AM, Mike Gilbert wrote:
>> I would like to remove the ban on variable references in the HOMEPAGE
>> variable in ebuilds.
>>
>
> What ban are you referring to? The Portage Manager Specification doesn't
> say anything of t
On czw, 2017-08-03 at 14:21 -0400, Michael Orlitzky wrote:
> On 08/03/2017 11:33 AM, Mike Gilbert wrote:
> > I would like to remove the ban on variable references in the HOMEPAGE
> > variable in ebuilds.
> >
>
> What ban are you referring to? The Portage Manager Specification doesn't
> say anythi
On 08/03/2017 11:33 AM, Mike Gilbert wrote:
> I would like to remove the ban on variable references in the HOMEPAGE
> variable in ebuilds.
>
What ban are you referring to? The Portage Manager Specification doesn't
say anything of the sort.
Seriously though, whatever sort of tricks your opponents
Hi Mike,
> I would like to remove the ban on variable references in the HOMEPAGE
> variable in ebuilds.
>
> As I understand it, this ban was put in place so that people can
> easily copy/paste from an ebuild to a web browser.
It made it also possible to grep through the packages and find thousan
On czw, 2017-08-03 at 11:33 -0400, Mike Gilbert wrote:
> I would like to remove the ban on variable references in the HOMEPAGE
> variable in ebuilds.
>
> As I understand it, this ban was put in place so that people can
> easily copy/paste from an ebuild to a web browser.
>
> If people want to cop
I would like to remove the ban on variable references in the HOMEPAGE
variable in ebuilds.
As I understand it, this ban was put in place so that people can
easily copy/paste from an ebuild to a web browser.
If people want to copy/paste the URL, they can easily query the final
value using the port
Michał Górny wrote:
>
> I have been running such a layout for over a year. [...]
Thanks for clarifying that this already was discussed.
Obviously, I was not aware about this discussion, and perhaps
I was not the only one.
> instead of waking up last-minute to redesign [...]
Pointing me to the d
On 20/07/2017 11:38, Kristian Fiskerstrand wrote:
> On 07/19/2017 09:24 PM, Paweł Hajdan, Jr. wrote:
>> * 4 files being committed...
>> error: gpg failed to sign the data
>> fatal: failed to write commit object
>> !!! Exiting on git (shell) error code: 128
>
> you can increase gpg-agent logging ve
On czw, 2017-08-03 at 07:50 +, Martin Vaeth wrote:
> Mike Gilbert wrote:
> > Debian puts 64-bit libs in /lib/(host)
>
> Yes, this is somewhat weird:
> They have /lib/i386-linux-gnu/ and /lib/x86_64-linux-gnu/
> but anyway they use /lib32 instead of e.g. /lib/i686-linux-gnu/
> Their reasons fo
Mike Gilbert wrote:
> Debian puts 64-bit libs in /lib/(host)
Yes, this is somewhat weird:
They have /lib/i386-linux-gnu/ and /lib/x86_64-linux-gnu/
but anyway they use /lib32 instead of e.g. /lib/i686-linux-gnu/
Their reasons for this are mysterious to me.
> Migrating Gentoo to a "multiarch" con
Michał Górny wrote:
>
> 'No mainstream' as you claim it doesn't mean it's fine to invent yet
> another completely incompatible solution.
As I understand, the compatibility with Debian might be increased
(keeping /lib32), at the cost of slightly decreasing the compatibility
with Red Hat (concernin
24 matches
Mail list logo
