CentOS - Feb 2017 - Licence text questions

On Sat, Feb 11, 2017 at 08:06:49AM -0500, Jonathan Billings wrote
> Wouldn't this be easier done as a mock chroot?  I realize you're
> not building RPMs, but you could use the chroot for building any
> software, and on any arbitrary CentOS or Fedora system.
  1) Not everybody runs Fedora/Redhat/CentOS

  2) The builds I'm doing are targetted at distros, like Puppy linux,
which use older libs with backported security fixes.  Pale Moon built
in a chroot or mock chroot in CentOS 6.8 and up, let alone any modern
distro, does not run on "Lucid Puppy" linux.  That's because
it'll
expect the newer libs on the target machine.  This is why I have to
provide the entire old CentOS 6.5 environment complete with older libs
to build against.

-- 
Walter Dnes <waltdnes at waltdnes.org>

> On Feb 11, 2017, at 10:57 AM, Walter Dnes <waltdnes at waltdnes.org>
wrote:
> 
>  2) The builds I'm doing are targetted at distros, like Puppy linux,
> which use older libs with backported security fixes.  Pale Moon built
> in a chroot or mock chroot in CentOS 6.8 and up, let alone any modern
> distro, does not run on "Lucid Puppy" linux.  That's because
it'll
> expect the newer libs on the target machine.  This is why I have to
> provide the entire old CentOS 6.5 environment complete with older libs
> to build against.

The point I was making is to make the old CentOS 6.5 environment as a chroot. 
Or maybe a docker container?  Something that you could spin up on a secure OS?

For that matter, you could probably just build a Puppy Linux docker container.

--
Jonathan Billings <billings at negate.org>

On Sun, Feb 12, 2017 at 10:43:39AM -0500, Jonathan Billings wrote
> The point I was making is to make the old CentOS 6.5 environment as
> a chroot.
  That's exactly my intention.  As I said in my original message...
>>  * or send out a 1.3 gigabyte centos65.tar.xz and give simple
>>    instructions to extract the archive, copy over /etc/resolv.conf,
>>    bind-mount /dev and /proc, chroot into the directory, and get
>>    going right away.
  The point of my first post was to ask about licencing.  Regardless of
whether I'm sending out a bootable ISO, or a QEMU disk image, or a
tarred up chrootable directory, I'm re-distributing Open Source code
and/or binaries, which I assume requires appropriate pointers to where
they can be obtained.

-- 
Walter Dnes <waltdnes at waltdnes.org>