From: "William L. Thomson Jr." <wlt-ml@o-sinc.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Prevent binary/non-compiled packages from binary package creation
Date: Wed, 9 Aug 2017 16:42:35 -0400 [thread overview]
Message-ID: <assp.039434facb.20170809164235.60083e5c@o-sinc.com> (raw)
In-Reply-To: <assp.0393730719.20170808123742.6e2e8d56@o-sinc.com>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
Just to clarify, the contenders for no binpkg would be the
following, potentially more.
- ebuilds that are fetch restricted
- ebuilds that installs files unchanged, like kernel sources
- Binary ebuilds, -bin, that just use src_install and do not build
anything
There may be some other cases, but I think that covers the main ones.
The first case, should NEVER, not even optionally be allowed to be
binpkg. That is re-distributing something that is fetch restricted. If
it cannot be mirrored, I doubt it can legally be re-packaged.
The later 2 could be "optional" defaulted to not build, but could be
forced. There is little benefit at that point but some may prefer those
be a binpkg.
I have no problem with it being optional.
--
William L. Thomson Jr.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-08-09 20:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 16:37 [gentoo-dev] Prevent binary/non-compiled packages from binary package creation William L. Thomson Jr.
2017-08-08 16:53 ` Rich Freeman
2017-08-08 17:11 ` Kristian Fiskerstrand
2017-08-08 17:18 ` Rich Freeman
2017-08-08 17:32 ` Michał Górny
2017-08-08 17:33 ` William L. Thomson Jr.
2017-08-08 17:23 ` William L. Thomson Jr.
2017-08-08 17:32 ` Kristian Fiskerstrand
2017-08-08 18:20 ` William L. Thomson Jr.
2017-08-08 18:41 ` William L. Thomson Jr.
2017-08-09 0:29 ` Sam Jorna (wraeth)
2017-08-09 0:43 ` William L. Thomson Jr.
2017-08-09 1:07 ` Sam Jorna (wraeth)
2017-08-09 15:33 ` William L. Thomson Jr.
2017-08-09 20:23 ` Francesco Riosa
2017-08-09 20:35 ` William L. Thomson Jr.
2017-08-10 0:50 ` Sam Jorna (wraeth)
2017-08-10 1:42 ` William L. Thomson Jr.
2017-08-10 3:33 ` Sam Jorna (wraeth)
2017-08-10 17:08 ` William L. Thomson Jr.
2017-08-10 23:58 ` Sam Jorna (wraeth)
2017-08-10 1:25 ` Sam Jorna (wraeth)
2017-08-10 1:47 ` William L. Thomson Jr.
2017-08-10 1:56 ` Sam Jorna (wraeth)
2017-08-08 17:34 ` Ian Stakenvicius
2017-08-08 18:10 ` William L. Thomson Jr.
2017-08-08 18:15 ` Kristian Fiskerstrand
2017-08-08 18:33 ` William L. Thomson Jr.
2017-08-09 20:42 ` William L. Thomson Jr. [this message]
2017-08-10 23:30 ` [gentoo-dev] " Duncan
2017-08-11 2:06 ` William L. Thomson Jr.
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=assp.039434facb.20170809164235.60083e5c@o-sinc.com \
--to=wlt-ml@o-sinc.com \
--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