public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: DESCRIPTION="Based on the ${ECLASS} eclass"
Date: Sat, 15 Sep 2012 14:59:00 +0000 (UTC)	[thread overview]
Message-ID: <pan.2012.09.15.14.59.00@cox.net> (raw)
In-Reply-To: CAATnKFDOhUHNwPNL0EUFNk1t6D1jft+edXFLbYxzifMHOCff6g@mail.gmail.com

Kent Fredric posted on Sat, 15 Sep 2012 23:52:16 +1200 as excerpted:

> If the usecase for this is "Sometimes people will want to write an
> ebuild and not provide a description at all, and don't care that its not
> useful",
> then it shoudn't be supported by a nasty hack in the parent eclass,
> Portage should instead support a missing DESCRIPTION feature.

Ciaranm already posted this link, from an earlier discussion, that 
describes why that thing's there.  It's legacy and it /should/ be gotten 
rid of I think most would agree (I certainly do as a user; it's a hassle 
and an eyesore).  Only nobody has cared to take on the responsibility of 
double-checking to make sure removing it doesn't break anything and of 
fixing anything they miss if it does anyway, so there the cruft still 
sits.

http://article.gmane.org/gmane.linux.gentoo.devel/78813/

Bottom line, I doubt there'd be any complaints if those lines 
"disappeared", as long as anything broken in the process equally 
magically just "got fixed".

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



      reply	other threads:[~2012-09-15 15:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 20:51 [gentoo-dev] DESCRIPTION="Based on the ${ECLASS} eclass" Rick "Zero_Chaos" Farina
2012-09-14 20:56 ` Ciaran McCreesh
2012-09-14 21:18   ` Rick "Zero_Chaos" Farina
2012-09-14 21:27     ` Michał Górny
2012-09-14 23:43       ` Rick "Zero_Chaos" Farina
2012-09-15  4:16         ` Mike Gilbert
2012-09-15  7:59         ` Michał Górny
2012-09-15 19:13           ` Rick "Zero_Chaos" Farina
2012-09-17  8:41           ` Markos Chandras
2012-09-15 15:06         ` [gentoo-dev] " Duncan
2012-09-15 17:01           ` Zac Medico
2012-09-16  3:30             ` Duncan
2012-09-15  0:23 ` [gentoo-dev] " Mike Frysinger
2012-09-15  9:01 ` Sergei Trofimovich
2012-09-15 11:52 ` Kent Fredric
2012-09-15 14:59   ` Duncan [this message]

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=pan.2012.09.15.14.59.00@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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