public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: RFC: Forbid using versions in DESCRIPTION
Date: Tue, 24 Jul 2007 15:06:40 +0300	[thread overview]
Message-ID: <46A5EB50.8080109@gentoo.org> (raw)
In-Reply-To: <f84pop$6nb$1@sea.gmane.org>

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

Tiziano Müller kirjoitti:
> Petteri Räty schrieb:
>> Currently there are some ebuilds in the tree that use ${PV} in
>> description which leads to results like:
>>      Description:         Documentation (including API Javadocs) for
>> Java SDK version 1.6.0
>>
>> I did see anything in devmanual taking a stance on this issue:
>> http://devmanual.gentoo.org/ebuild-writing/variables/index.html
>> What do you think about adding a sentence or two saying that you should
>> not use version numbers in DESCRIPTION? This could even be added to repoman.
> 
> As far as I understood it, having DESCRIPTION in the ebuild itself
> (rather than in metadata) means that DESCRIPTION is allowed to change
> between versions, whether "automatically" by using a version-dependent
> variable or "manually".
> 
> I'd therefore only add a note in the devmanual which recommends not to
> use ${PV} (and ${P}, ...) in the DESCRIPTION.
> 
> Cheers,
> Tiziano
> 

But is there anything that makes use of version specific DESCRIPTION atoms?

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2007-07-24 12:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 11:11 [gentoo-dev] RFC: Forbid using versions in DESCRIPTION Petteri Räty
2007-07-24 11:36 ` [gentoo-dev] " Christian Faulhammer
2007-07-24 11:44   ` Marijn Schouten (hkBst)
2007-07-24 11:54     ` David Shakaryan
2007-07-24 12:04     ` Petteri Räty
2007-07-24 13:22       ` Tiziano Müller
2007-07-24 12:16     ` Ciaran McCreesh
2007-07-24 12:26       ` Petteri Räty
2007-07-24 13:09         ` Robert Buchholz
2007-07-24 13:18       ` Tiziano Müller
2007-07-24 13:30         ` Ciaran McCreesh
2007-07-24 13:46           ` Luca Barbato
2007-07-24 13:55             ` Ciaran McCreesh
2007-07-24 14:11               ` Luca Barbato
2007-07-24 14:21                 ` Ciaran McCreesh
2007-07-24 14:46                   ` Tiziano Müller
2007-07-24 13:36     ` Luca Barbato
2007-07-25 12:17       ` Mike Frysinger
2007-07-24 12:02 ` Tiziano Müller
2007-07-24 12:06   ` Petteri Räty [this message]
2007-07-24 12:14     ` Ciaran McCreesh
2007-07-24 12:18       ` Petteri Räty
2007-07-24 13:14         ` Tiziano Müller
2007-07-24 12:53       ` Marijn Schouten (hkBst)
2007-07-25 12:15       ` Mike Frysinger
2007-07-24 12:12   ` David Shakaryan

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=46A5EB50.8080109@gentoo.org \
    --to=betelgeuse@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