public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Ammerlaan <andrewammerlaan@riseup.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New project: binhost
Date: Thu, 11 Feb 2021 15:00:38 +0100	[thread overview]
Message-ID: <3d4f739e-df4f-db1b-52bc-094c74ff1c10@riseup.net> (raw)
In-Reply-To: <24819743.1r3eYUQgxm@farino>

On 10/02/2021 18:57, Andreas K. Hüttel wrote:
> Hi all,
> 
> I'm announcing a new project here - "binhost"
> 
> "The Gentoo Binhost project aims to provide readily installable, precompiled
> packages for a subset of configurations, via central binary package hosting.
> Currently we are still in the conceptual planning stage. "
> 
> https://wiki.gentoo.org/wiki/Project:Binhost
> 
> If you're interested in helping out, feel free to add yourself on the wiki
> page.
> 
> Note that I see actually *building* the packages not as the central point of
> the project (that could be e.g. a side effect of a tinderbox). I'm more
> concerned about
> * what configurations should we use

Others have already suggested starting with a minimal set of flags or 
starting with the profiles, and then adding flags at request. I would 
like to suggest the opposite approach, start with binpkgs of packages 
which have all or most of the flags enabled, and then add more 
specific/minimal configurations of that package later. Because from an 
user perspective it is less of a problem to install a binpkg which has 
more features than you need, than it is to install a binpkg which is 
lacking a certain feature you need. Therefore, I would start with 
configurations of packages that have most/all things enabled, and thus 
are usable for the largest amount of people. This would pull in more 
dependencies, but for binpkgs this is less of a problem since they don't 
add compile time.

> * what portage features are still needed or need improvements (e.g. binpkg
> signing and verification)

I think a bugtracker for this might be a good idea at some point. In 
general, I think that portage's binpkg support is very good already, 
there are however some things that could be improved. Bug 
https://bugs.gentoo.org/687668 comes to mind (and some other things that 
were already mentioned by others).

The wiki guide on binpkgs[1] also mentions that:
"""
The support for multiple binary package servers is somewhat incomplete. 
If several servers serve a binary package for the same package version, 
then only the first one will be considered. This can be problematic when 
these binary packages differ in their USE variable configuration and the 
USE variable configuration of a later binary package would match the 
systems configuration.
"""
I don't know if this is still accurate, but if it is that would 
definitely be something that could use some improvement.

[1] https://wiki.gentoo.org/wiki/Binary_package_guide

> * how should hosting look like
> * and how we can test this on a limited scale before it goes "into production"
> * ...
> 
> Comments, ideas, flamebaits? :D
> 
> Cheers,
> Andreas
> 





  parent reply	other threads:[~2021-02-11 14:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 17:57 [gentoo-dev] New project: binhost Andreas K. Hüttel
2021-02-10 18:51 ` Lars Wendler
2021-02-11  9:17   ` Michał Górny
2021-02-14  0:37     ` Zac Medico
2021-02-14  0:53       ` Zac Medico
2021-02-21  4:17         ` Zac Medico
2021-02-21 16:57           ` Andreas K. Huettel
2021-02-23 19:46           ` Zac Medico
2021-02-23 20:05             ` Zac Medico
2021-02-23 20:33               ` Zac Medico
2021-02-24 10:29                 ` Zac Medico
2021-02-24 12:13                   ` Zac Medico
2021-02-14  0:29   ` Zac Medico
2021-02-16  1:50   ` Francesco Riosa
2021-02-16  7:58     ` Jaco Kroon
2021-02-10 18:51 ` Aisha Tammy
2021-02-10 19:11 ` Rich Freeman
2021-02-10 19:15   ` Andreas K. Hüttel
2021-02-16  1:37     ` Francesco Riosa
2021-02-10 19:16   ` Aisha Tammy
2021-02-10 23:19   ` Alexey Sokolov
2021-02-11  9:41   ` Jaco Kroon
2021-02-14  1:51   ` Zac Medico
2021-02-14 13:30     ` Rich Freeman
2021-02-23 19:53     ` Zac Medico
2021-02-10 20:04 ` Frédéric Pierret
2021-03-13 12:25   ` Frédéric Pierret
2021-02-10 21:34 ` Toralf Förster
2021-02-11 14:00 ` Andrew Ammerlaan [this message]
2021-02-13  3:32 ` Marc Schiffbauer
2021-02-13  4:21 ` Aisha Tammy
2021-02-13  9:13 ` Michael Jones
2021-02-13 12:08 ` m1027
2021-02-15 14:20 ` [gentoo-dev] " Michael Haubenwallner
2021-03-13  8:43 ` [gentoo-dev] " Torokhov Sergey
2021-03-13 10:47   ` Marco Scardovi
2021-03-13 11:58     ` Wolfgang E. Sanyer
2021-03-14 21:12     ` Torokhov Sergey

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=3d4f739e-df4f-db1b-52bc-094c74ff1c10@riseup.net \
    --to=andrewammerlaan@riseup.net \
    --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