From: Brandon Low <lostlogic@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: Misc questions on ebuilds
Date: Sun, 16 Jun 2002 01:12:01 -0500 [thread overview]
Message-ID: <20020616011201.A15702@lostlogicx.com> (raw)
In-Reply-To: <6u5ngu8ocssir508h6v6a9ns2kk4klrkie@4ax.com>; from spamtrap@ruddygore.net on Sat, Jun 15, 2002 at 08:53:04PM +0100
The current policy is to explicitly define everything as lintool asks...
for many/most ebuilds RDEPEND="${DEPEND}" works for now... SLOT is
semi-optional, but for a new package, just make it SLOT="0" for
consistency...
--Brandon
On Sat, 06/15/02 at 20:53:04 +0100, Mark Gordon wrote:
> On Fri, 14 Jun 2002 22:56:29 -0500, Brandon Low <lostlogic@gentoo.org>
> wrote:
>
> >Have you used the "lintool" script that comes with gentoolkit? It is a
> >nice tool which checks for most common ebuilding mistakes...
>
> Some questions about that. Looking at skel.ebuild I thought that
> RDEPEND did not need to be defined since it would default to DEPEND,
> yet lintool considers not defining it an error.
>
> Is it considered better to allow things to default when the documented
> defaults are correct or to explicitly define everything, in which case
> I would have thought the skel.ebuild should tell you the normal values
> but not say they are defaults for when items are not specified.
>
> I've already submitted one ebuild and hope to submit more, so I want
> to get them as 'correct' as possible.
> --
> Mark Gordon
>
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2002-06-16 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-15 3:21 [gentoo-dev] Misc questions on ebuilds Keith Gross
2002-06-15 3:56 ` Brandon Low
2002-06-15 19:53 ` [gentoo-dev] " Mark Gordon
2002-06-16 6:12 ` Brandon Low [this message]
2002-06-16 18:40 ` [gentoo-dev] " Marcelo Fontenele S Santos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020616011201.A15702@lostlogicx.com \
--to=lostlogic@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox