From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: new global USE flag "srcdist"
Date: Thu, 2 Jan 2014 13:54:12 +0100 [thread overview]
Message-ID: <21189.24948.162463.335486@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <52C4D3E4.6060308@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
>>>>> On Wed, 01 Jan 2014, Michael Orlitzky wrote:
> As I said in another reply, more license metadata is good and we
> should make it available. But a USE flag that changes the meaning of
> an important global variable is a little hacky, especially if it
> doesn't solve a real problem within Gentoo/Portage.
A srcdist flag wouldn't be that much different from the bindist flag
that we already have, and which is also of a non-technical nature.
> If the problems are theoretical (or aren't Gentoo package management
> problems), maybe it's better to wait and do it right in an EAPI.
As I said, this would leave us with a long transition period. And what
syntax would you propose? Additional license variables? Or Exherbo
style depend syntax? TBH, I don't want to open this can of worms. ;-)
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-01-02 12:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 22:28 [gentoo-dev] RFC: new global USE flag "srcdist" Ulrich Mueller
2014-01-02 1:21 ` Rick "Zero_Chaos" Farina
2014-01-02 1:51 ` Michael Orlitzky
2014-01-02 2:10 ` Rich Freeman
2014-01-02 2:19 ` Michael Orlitzky
2014-01-02 2:38 ` Rich Freeman
2014-01-02 2:50 ` Michael Orlitzky
2014-01-02 2:57 ` Rich Freeman
2014-01-02 12:54 ` Ulrich Mueller [this message]
2014-01-02 15:25 ` Michael Orlitzky
2014-01-02 16:24 ` Rich Freeman
2014-01-02 11:35 ` Ulrich Mueller
2014-01-02 2:13 ` Rick "Zero_Chaos" Farina
2014-01-02 2:40 ` Michael Orlitzky
2014-01-02 2:43 ` Rick "Zero_Chaos" Farina
2014-01-02 8:56 ` Michał Górny
2014-01-02 12:45 ` Ulrich Mueller
2014-01-02 12:50 ` [gentoo-dev] " Ryan Hill
2014-01-02 12:54 ` Ryan Hill
2014-01-02 13:18 ` Ulrich Mueller
2014-01-02 14:07 ` Kent Fredric
2014-01-02 14:01 ` Kent Fredric
2014-01-02 16:10 ` Ian Stakenvicius
2014-01-02 16:28 ` Luis Ressel
2014-01-02 16:37 ` Kent Fredric
2014-01-02 17:02 ` Luis Ressel
2014-01-03 14:09 ` Kent Fredric
2014-01-02 16:53 ` Ulrich Mueller
2014-01-02 17:02 ` Luis Ressel
2014-01-02 18:17 ` Ulrich Mueller
2014-01-02 18:27 ` Rich Freeman
2014-01-02 18:34 ` Ulrich Mueller
2014-01-02 21:11 ` Ryan Hill
2014-01-02 21:20 ` Rich Freeman
2014-01-02 22:07 ` Ryan Hill
2014-01-02 22:53 ` Ryan Hill
2014-01-02 23:53 ` Ulrich Mueller
2014-01-05 3:00 ` Ryan Hill
2014-01-02 17:13 ` Ian Stakenvicius
2014-01-02 18:25 ` Luis Ressel
2014-01-02 21:24 ` Ryan Hill
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=21189.24948.162463.335486@a1i15.kph.uni-mainz.de \
--to=ulm@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