From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "William L. Thomson Jr." <wlt-ml@o-sinc.com>
Subject: Re: [gentoo-dev] Prevent binary/non-compiled packages from binary package creation
Date: Tue, 08 Aug 2017 19:32:18 +0200 [thread overview]
Message-ID: <1502213538.16996.0.camel@gentoo.org> (raw)
In-Reply-To: <CAGfcS_mB5Fgo3SdJMruhL4vqa81v2da1TRfS6ky5W+=FmO1gvA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
On wto, 2017-08-08 at 10:18 -0700, Rich Freeman wrote:
> On Tue, Aug 8, 2017 at 10:11 AM, Kristian Fiskerstrand <k_f@gentoo.org> wrote:
> > On 08/08/2017 06:37 PM, William L. Thomson Jr. wrote:
> > > I make a lot of binaries for use on other systems, to expedite updates.
> > > It does not make sense for some packages to ever be a binary package.
> >
> > Any particular reason this decision shouldn't be left to the operator of
> > the binhost rather than the package maintainer? it can already be
> > controlled through env files.
> >
>
> Perhaps, but I could see some value in having some way to mark
> packages that don't compile anything. This could also overlap
> somewhat with the desire to track arch-independent packages for
> stabilization purposes. I could see it being useful to be able to
> obtain a list of all the binary packages in the Gentoo repo for QA
> purposes/etc as well.
>
> Maybe it isn't a flag that outright blocks binary package building,
> but a way to mark such packages so that a user can apply a policy on
> top of this.
>
> Whether it belongs in the ebuild, or in metadata, is another matter.
Does a package that builds documentation from sources count?
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 988 bytes --]
next prev parent reply other threads:[~2017-08-08 17:32 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 [this message]
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.
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=1502213538.16996.0.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=wlt-ml@o-sinc.com \
/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