Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Samuli Suominen <ssuominen@g.o>
Subject: Re: skel.ebuild cosmetics (move RESTRICT after DEPEND)
Date: Mon, 07 May 2012 01:33:26 +0300
On 05/07/2012 01:27 AM, Ulrich Mueller wrote:
>>>>>> On Mon, 07 May 2012, Samuli Suominen wrote:
>
>> If you `vim foo.ebuild` the default template will automatically
>> include lines for DEPEND and RDEPEND, but not for RESTRICT
>
> Are we now using behaviour of editors as a reference? With Emacs or
> XEmacs, the template includes RESTRICT and places it before DEPEND and
> RDEPEND.

I would rather see RESTRICT dropped from the template included for 
emacs, because it's not expected for majority of ebuilds to have need 
for it (a fact).
The template for emacs should be kept in sync with the example for vim 
(or whichever way around).

>
>> Therefore I suggest we move this example a bit down in skel.ebuild
>> as it's more logical to continue with new lines instead of applying
>> in-between
>
>> Any objections?
>
> Yes. Please leave it as it is.

Yeah, I will if someone has a (good) argument for doing so.


Replies:
Re: skel.ebuild cosmetics (move RESTRICT after DEPEND)
-- Ulrich Mueller
References:
skel.ebuild cosmetics (move RESTRICT after DEPEND)
-- Samuli Suominen
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: skel.ebuild cosmetics (move RESTRICT after DEPEND)
Next by thread:
Re: skel.ebuild cosmetics (move RESTRICT after DEPEND)
Previous by date:
Re: skel.ebuild cosmetics (move RESTRICT after DEPEND)
Next by date:
Re: skel.ebuild cosmetics (move RESTRICT after DEPEND)


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.