Licence Text Questions

Home » CentOS » Licence Text Questions
CentOS 5 Comments

I’m running a CentOS 6.5 chroot to build Pale Moon (a Firefox fork)
for older machines running distros like Puppy linux. Before anyone asks…

* Yes, even though the older machines are using “ancient” glibc, etc,
they do have security patches back-ported, e.g.

5 thoughts on - Licence Text Questions

  • 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.

    Jonathan Billings

  • On Sat, Feb 11, 2017 at 08:06:49AM -0500, Jonathan Billings wrote

    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.

  • 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.

  • On Sun, Feb 12, 2017 at 10:43:39AM -0500, Jonathan Billings wrote

    That’s exactly my intention. As I said in my original message…

    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.