public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Santiago M. Mola" <coldwind@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RDEPEND definition in docs differ from official PMS specs
Date: Sat, 17 Jan 2009 16:52:11 +0100	[thread overview]
Message-ID: <1232207531.6645.13.camel@mangurrian> (raw)
In-Reply-To: <4971FC25.6040605@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]

El sáb, 17-01-2009 a las 16:41 +0100, Thomas Sachau escribió:
> Marius Mauch schrieb:
> > On Sat, 17 Jan 2009 14:09:49 +0100
> > Thomas Sachau <tommy@gentoo.org> wrote:
> > 
> >> Hi,
> >>
> >> as specified in the PMS spec [1] and stated in #gentoo-portage,
> >> RDEPEND will be set to DEPEND, if it is not defined in the ebuild
> >> itself. But devmanual [2] and developer handbook [3] both state, you
> >> have do explicitly set RDEPEND because it may be removed in the
> >> future. Since package manager have to follow the PMS spec, i would
> >> suggest to change those docs [2][3] and let them follow the PMS spec.
> >>
> >> Any problems, suggestions or anything else about this?
> > 
> > It's strongly recommended to set both explicitly as the behavior could
> > change in future EAPI versions, and to ensure that you actually think
> > about which deps are build deps and which are runtime deps.
> > Also there is nothing wrong with policies being stricter than the
> > underlying spec.
> > 
> > Marius
> > 
> > 
> 
> If i want to use some future EAPI (give me some reasons, why this should be changed there by
> default), i should think about it. But most ebuilds will stay with the default. I do think about
> runtime deps and build deps. In my eyes, this is similar to src_unpack and src_compile. They have
> defaults, noone specifies the defaults, even if they are changed in some EAPI.
> 

You may want to change the wording in docs to make it say it's
encouraged to set both but it's not technically needed.

Note that PMS is *not* a good practice guidelenes. There are a bunch of
things that are technically valid but wrong from a QA point of view.

Regards,
-- 
Santiago Moisés Mola
Jabber: cooldwind@gmail.com | GPG: AAD203B5

[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-01-17 15:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17 13:09 [gentoo-dev] RDEPEND definition in docs differ from official PMS specs Thomas Sachau
2009-01-17 13:24 ` Jan Kundrát
2009-01-17 14:38 ` Marius Mauch
2009-01-17 15:41   ` Thomas Sachau
2009-01-17 15:52     ` Santiago M. Mola [this message]
2009-01-17 17:02     ` Marius Mauch
2009-01-18  9:07       ` Peter Volkov
2009-01-18 11:21         ` Petteri Räty
2009-01-18 15:21           ` Ciaran McCreesh
2009-01-18 21:01             ` Maciej Mrozowski
2009-01-18 21:24               ` Petteri Räty
2009-01-18 21:52               ` Ciaran McCreesh

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=1232207531.6645.13.camel@mangurrian \
    --to=coldwind@gentoo.org \
    --cc=gentoo-dev@lists.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