public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William L. Thomson Jr." <wlt-ml@o-sinc.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Package file name requirement for binary ebuilds
Date: Mon, 17 Oct 2016 10:04:40 -0400	[thread overview]
Message-ID: <assp.009871b8f3.2129473.vsFFOgr5ef@wlt> (raw)
In-Reply-To: <4b4ed689-2c53-dce6-ca86-9ca200739481@gentoo.org>

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

On Monday, October 17, 2016 3:52:52 PM EDT Kristian Fiskerstrand wrote:
>
> Off the top of my head I'm only aware of libreoffice-bin myself (and
> then it is a clear alternative to libreoffice if wanting the source),
> providing this as a binary is a convenience to end-users not wanting to
> spend 50 minutes on the compile.

That seems to be the main use of -bin, and the reason for like icedtea-bin, 
and other firefox-bin, etc. I would not suggest get rid of those, though could 
be in a different place if it bothers others.

I have always used oo-bin, but did compile libreoffice. Never compiled oo it was 
way to big.  At a point have used firefox-bin, and icedtea-bin, when not 
wanting to merge those from source. Just being lazy and not wanting some of 
the dependencies.
 
> I'm wondering if it wouldn't make sense to provide this as a binary
> package in a binhost instead of a -bin though (thats what I use
> internally myself in any case).

I am not pushing for such, but BSD does have a binary ports tree I believe 
available separate from the from source. I make my own binaries for other 
systems, to speed up updates. But I do not really use a binhost.

Long ago there was some company that was doing a repo of precompiled Gentoo 
binaries. But it went away a very long time ago. I haven't seen anything 
attempt it since. Not sure the demand, but things like Arch do exist now.

As for packages in tree as bin that can be from source, I have already pointed 
one out, dev-util/jenkins-bin. There are others.

Even if we have a list, what next? There are reasons why they are not packaged 
from source, and that will not change. Good to be aware, but without any sort 
of plan or means to address. Not sure it will matter.

-- 
William L. Thomson Jr.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

  reply	other threads:[~2016-10-17 14:05 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 17:05 [gentoo-dev] Package file name requirement for binary ebuilds William L. Thomson Jr.
2016-10-14 17:09 ` Ian Stakenvicius
2016-10-14 17:17   ` William L. Thomson Jr.
2016-10-14 17:29     ` Ian Stakenvicius
2016-10-15 10:32     ` Kristian Fiskerstrand
2016-10-15 22:00       ` Austin English
2016-10-16 22:20         ` William L. Thomson Jr.
2016-10-17  8:21           ` Kent Fredric
2016-10-23  8:46             ` Daniel Campbell
2016-10-14 17:36 ` Mike Gilbert
2016-10-14 18:05   ` William L. Thomson Jr.
2016-10-14 18:15     ` Ulrich Mueller
2016-10-14 20:48       ` William L. Thomson Jr.
2016-10-17 17:41   ` Brian Evans
2016-10-14 21:00 ` William Hubbs
2016-10-14 21:10   ` William L. Thomson Jr.
2016-10-14 21:14   ` William L. Thomson Jr.
2016-10-15  3:10 ` Kent Fredric
2016-10-16 22:30   ` William L. Thomson Jr.
2016-10-17  1:19     ` Ian Stakenvicius
2016-10-17  2:43       ` William L. Thomson Jr.
2016-10-17  5:43         ` Ian Stakenvicius
2016-10-17 16:10           ` Michael Orlitzky
2016-10-17  4:37     ` [gentoo-dev] " Duncan
2016-10-17  5:36       ` William L. Thomson Jr.
2016-10-18  5:36         ` Duncan
2016-10-17  6:57     ` [gentoo-dev] " Michał Górny
2016-10-17  7:17       ` Ulrich Mueller
2016-10-17  7:30         ` M. J. Everitt
2016-10-17  7:41         ` William L. Thomson Jr.
2016-10-17  7:49           ` M. J. Everitt
2016-10-17 12:20             ` Ulrich Mueller
2016-10-17 13:44               ` William L. Thomson Jr.
2016-10-17 13:47                 ` M. J. Everitt
2016-10-17 13:52                   ` William L. Thomson Jr.
2016-10-17 13:56                     ` William L. Thomson Jr.
2016-10-17 14:11                     ` M. J. Everitt
2016-10-17 13:52                   ` Kristian Fiskerstrand
2016-10-17 14:04                     ` William L. Thomson Jr. [this message]
2016-10-17 14:09                       ` Kristian Fiskerstrand
2016-10-17 14:13                         ` M. J. Everitt
2016-10-17 14:34                           ` William L. Thomson Jr.
2016-10-17 14:54                     ` Michael Mol
2016-10-17 15:01                       ` Ian Stakenvicius
2016-10-17 15:10                         ` William L. Thomson Jr.
2016-10-17 15:00               ` Mike Gilbert
2016-10-17 15:09               ` Michał Górny
2016-10-17 16:08                 ` Ulrich Mueller
2016-10-17 16:51                 ` NP-Hardass
2016-10-17  8:46           ` Kent Fredric
2016-10-17 13:39             ` William L. Thomson Jr.
2016-10-17 15:02               ` Kent Fredric
2016-10-17  7:37       ` William L. Thomson Jr.
2016-10-17  7:40         ` Michał Górny
2016-10-17 13:40           ` William L. Thomson Jr.
2016-10-17 17:09         ` Michael Mol
2016-10-17 17:25           ` Kent Fredric
2016-10-17  8:29     ` Kent Fredric
2016-10-17 13:32       ` William L. Thomson Jr.
2016-10-17 15:18         ` Kent Fredric
2016-10-17 15:48           ` William L. Thomson Jr.
2016-10-17 16:08             ` Michał Górny
2016-10-17 16:18               ` William L. Thomson Jr.
2016-10-17 17:34                 ` Michał Górny
2016-10-17 20:03                   ` William L. Thomson Jr.
2016-10-17 20:34                     ` Michał Górny
2016-10-17 20:43                       ` William L. Thomson Jr.
2016-10-18 15:15                         ` Ciaran McCreesh

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.009871b8f3.2129473.vsFFOgr5ef@wlt \
    --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