public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: RFC: new global USE flag "srcdist"
Date: Sat, 4 Jan 2014 21:00:39 -0600	[thread overview]
Message-ID: <20140104210039.295d5523@caribou.gateway.pace.com> (raw)
In-Reply-To: 21189.64493.797568.198088@a1i15.kph.uni-mainz.de

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

On Fri, 3 Jan 2014 00:53:17 +0100
Ulrich Mueller <ulm@gentoo.org> wrote:

> >>>>> On Thu, 2 Jan 2014, Ryan Hill wrote:
> 
> > In case it's helpful here's what FOSSology[1] has to say about some
> > common packages that people have uploaded to their demo server.
> 
> I don't get your point here. The licenses of a package have to be
> checked in any case. Why would it be more complicated to check the
> full set of files in the tarball, instead of the subset of files that
> the package will actually install?

I was trying to see how many packages contain licenses that aren't already in
LICENSES, assuming these would be ones that we would have to have a srcdist USE
flag for.  Rich said that is was rare.  I'm finding every package I've checked
so far would need one.

Either way I don't care what you do.


-- 
Ryan Hill                        psn: dirtyepic_sk
   gcc-porting/toolchain/wxwidgets @ gentoo.org

47C3 6D62 4864 0E49 8E9E  7F92 ED38 BD49 957A 8463

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2014-01-05  2:51 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
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 [this message]
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=20140104210039.295d5523@caribou.gateway.pace.com \
    --to=dirtyepic@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