Openela releases Red Hat source code on GitHub
1–10 of 57 posts
Re: Openela releases Red Hat source code on GitHub
#2I wonder if this consortium will end up defining "enterprise" Linux in the same way that POSIX forcibly seized the standards for UNIX from the control of AT&T and Sun.
Re: Openela releases Red Hat source code on GitHub
#3This is likely just defining a baseline to build on or off of. Ideally off.
Re: Openela releases Red Hat source code on GitHub
#4I'm an avid Linux user, but never heard of OpenELA before.
Re: Openela releases Red Hat source code on GitHub
#5I'm an avid Linux user, but never heard of OpenELA before.
It’s less than 3 months old.
Re: Openela releases Red Hat source code on GitHub
#6I wonder what it means for SuSE Enterprise Linux in the long run.
Are they going to migrate SLE to be bug-for-bug RHEL compatible but keep their own tools on top? What about OpenSUSE? I'm an avid SLE/OpenSUSE user and it was chosen specifically because it's not an RHEL clone.
Re: Openela releases Red Hat source code on GitHub
#7it's 3000 repositories - one per package- all containing just a spec file and some patches. How is this remotely maintainable? Is this also how redhat upstream works? (I'm coming from nixpkgs where everything is in one mono-repo; which is great for cross-cutting concerns)
How do you make cross-operating system changes? Or are they just planning to ship Redhat verbatim and never make their own stuff?
Re: Openela releases Red Hat source code on GitHub
#8it's 3000 repositories - one per package- all containing just a spec file and some patches. How is this remotely maintainable? Is this also how redhat upstream works? (I'm coming from nixpkgs where everything is in one mono-repo; which is great for cross-cutting concerns) How do you make cross-operating system changes? Or are they just planning to ship Redhat verbatim and never make their own stuff?
At least in Fedora it’s exactly like that: many repos, one per source package. Guess CentOS/RHEL are doing it in the same fashion.
Fedora has had 39 versions so far, it’s alive and kicking, so my guess is it’s maintainable enough.
Re: Openela releases Red Hat source code on GitHub
#9it's 3000 repositories - one per package- all containing just a spec file and some patches. How is this remotely maintainable? Is this also how redhat upstream works? (I'm coming from nixpkgs where everything is in one mono-repo; which is great for cross-cutting concerns) How do you make cross-operating system changes? Or are they just planning to ship Redhat verbatim and never make their own stuff?
I'd say the majority of distributions work this way. At least Debian[1], Fedora/CentOS/RHEL[2], SUSE[3], Arch[4], ...
[1] https://salsa.debian.org/public
[2] https://gitlab.com/redhat/centos-stream/rpms
[3] https://build.opensuse.org/project/show/openSUSE:Factory
[4] https://gitlab.archlinux.org/archlinux/packaging/packages
Re: Openela releases Red Hat source code on GitHub
#10I wonder what it means for SuSE Enterprise Linux in the long run. Are they going to migrate SLE to be bug-for-bug RHEL compatible but keep their own tools on top? What about OpenSUSE? I'm an avid SLE/OpenSUSE user and it was chosen specifically because it's not an RHEL clone.
SuSE uses btrfs for the root filesystem, and although this can be quite dangerous if it fills up, it does allow much greater flexibility in rolling back the OS to a working state.
It would be interesting if this capability returned to OpenELA. It could be done with rhel7 (and clones).
There are likely some users who consider this a must-have.