public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo chroot with old glibc
Date: Sun, 21 Jun 2020 17:08:14 -0400	[thread overview]
Message-ID: <CAGfcS_=DKGeeRO1amOzY5KjOL9eH2fO1SoZn=6y-kjq2mg3Skg@mail.gmail.com> (raw)
In-Reply-To: <2061dce3-a6b3-31a7-aed0-c08487fa15ce@apteryx.fr>

On Fri, Jun 19, 2020 at 5:19 PM Hervé Guillemet <hg@apteryx.fr> wrote:
>
> Or do you have any suggestion for alternatives to this gentoo chroot ?
> (I'd prefer avoid installing some CentOS or Ubuntu as virtual guests).

You're of course free to do it any way you wish, but if I wanted to
create packages for various distros, I'd probably just follow their
instructions for doing so.

If you're making Ubuntu 16.04 packages I suspect it would be just a
lot less fuss all around to do it from an Ubuntu 16.04 container, and
so on.

And if you're just building binaries and creating tarballs with them,
well, why?  If people want to manually deal with stuff the source is
already fine.  If they want the benefits of a package manager they're
going to want packages.  And if you're hoping to encourage distros to
do the packaging for you, they're probably only going to do that from
source anyway.

I imagine most distros have a fairly straightforward packaging system,
and I suspect a lot of CI systems have plugins to churn out packages
for them automatically.  So why maintain some Gentoo chroot and
carefully curate every single library on them to match some entirely
different distro?  You're going to run into stuff where Gentoo doesn't
have the version you need in the repo, and you'll be fighting auto
updates, and so on.

But, sure, you can get Gentoo to install whatever you want as long as
you don't mind manually picking packages, or maintaining your own repo
where you carefully curate this stuff.

-- 
Rich


  parent reply	other threads:[~2020-06-21 21:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 21:19 [gentoo-user] Gentoo chroot with old glibc Hervé Guillemet
2020-06-21 17:06 ` Michael
2020-06-21 19:43   ` Hervé Guillemet
2020-06-21 20:03     ` Michael
2020-06-21 22:52       ` Hervé Guillemet
2020-06-30  8:26     ` Andreas K. Huettel
2020-06-30 16:29       ` Laurence Perkins
2020-07-01  1:40         ` [gentoo-user] Grub: for the love of almighty Zardoz the magniicent Alan Grimes
2020-07-01  8:15           ` Neil Bothwick
2020-07-01  8:45             ` Michael
2020-07-02  4:20               ` Alan Grimes
2020-07-01  1:30       ` [gentoo-user] Gentoo chroot with old glibc Thomas Mueller
     [not found]       ` <20200701013122.CE9C8E08AE@pigeon.gentoo.org>
2020-07-01 14:47         ` Andreas K. Huettel
2021-01-04 11:57       ` Thomas Mueller
     [not found]       ` <20210104115748.50A5EE0930@pigeon.gentoo.org>
2021-01-08 23:37         ` Andreas K. Hüttel
2020-06-21 21:08 ` Rich Freeman [this message]
2020-06-21 22:34   ` Hervé Guillemet

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='CAGfcS_=DKGeeRO1amOzY5KjOL9eH2fO1SoZn=6y-kjq2mg3Skg@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@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