public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: m1027 <m1027@posteo.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New project: binhost
Date: Sat, 13 Feb 2021 13:08:34 +0100	[thread overview]
Message-ID: <YCfBQjce+Fq/iqC5@host> (raw)
In-Reply-To: <24819743.1r3eYUQgxm@farino>

dilfridge:

> 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
> * what portage features are still needed or need improvements (e.g. binpkg 
> signing and verification)
> * how should hosting look like
> * and how we can test this on a limited scale before it goes "into production"
> * ...
> 
> Comments, ideas, flamebaits? :D

What's with CFLAGS?

I haven't been working with pre-built binary packages yet. But I
imagine something flexible, between distant compiler and a server
keeping the binaries. For my cases, from Raspberry Pis up to AMD
Ryzens, I love to have this server to just receive the requests what
and how to compile and keep exactly the packages which are
requested so it can be distributed if requested again.

Thanks



  parent reply	other threads:[~2021-02-13 12:08 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
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 [this message]
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=YCfBQjce+Fq/iqC5@host \
    --to=m1027@posteo.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