Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Openela releases Red Hat source code on GitHub

github.com

Post reply on HN
Print view View original

11–20 of 57 posts

Re: Openela releases Red Hat source code on GitHub

#11

Post by eraser215 »

arianvanp wrote: post #7

it'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?

"Or are they just planning to ship Redhat verbatim and never make their own stuff?"

That is their stated mission.

Re: Openela releases Red Hat source code on GitHub

#12

Post by nolist_policy »

chasil wrote: post #10
fffrantz wrote: post #6

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

I can guarantee you that SuSE will only ever support btrfs with their own kernel. There are a ton of fixes backported in theirs. At which point you are running SLES anyway.

Re: Openela releases Red Hat source code on GitHub

#13

Post by tempay »

arianvanp wrote: post #7

it'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?

In general I'd say nixpkgs is more of an outlier, though the nature of nix makes it a bit different to other package ecosystems.

I've contributed to both models and you just end up with a lot of tooling and bots. One of the benifits of the repo-per-package approach is that you can have different maintainers for different package which is a bit tricker with a monorepo.

Re: Openela releases Red Hat source code on GitHub

#19

Post by rwmj »

arianvanp wrote: post #7

it'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?

That's how things were distributed by CentOS.

Re: Openela releases Red Hat source code on GitHub

#20

Post by spandextwins »

eraser215 wrote: post #11
arianvanp wrote: post #7

it'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?

"Or are they just planning to ship Redhat verbatim and never make their own stuff?" That is their stated mission.

Anybody can do that with open source as long as they make the source code available. That shouldn't surprise anyone. Source code is free and open.
Post reply on HN