@bagder Yes, you definitely need accompanying documents. Doxygen does a good job at extracting the API documentation, but that's it. Expecting that to be enough, is like expecting someone to be able to chart a forest after you explained them every tree (in a rather arbitrary order).
After years of sniffing at it curiously, I started poking around with the #i3 DE on #Fedora. It feels like there's a lot to learn and that it can be a bit of a time sink, and honestly, I'm all in.
@vwbusguy@johanneskastl@sfalken There will be no SLES 16 and #ALP will definitely offer a non-transactional variant as well. Whichever will become the default, will probably be a source of much bike-shedding in the months to come 😉
While you can force rpm to install a RHEL rpm package on SLES, it will most likely not even install cleanly, let alone run. Oracle Linux is an entirely different story, as it aims to be a 1:1 rebuild of RHEL.
@resuna@passthejoe@Conan_Kudo@vwbusguy@gnuplusmatt@adamw@carlwgeorge Could be, but you shouldn't rely on SLES and RHEL being compatible. They might be mostly compatible, but there's enough naming differences, package version mismatches, configuration discrepancies, etc. that I really wouldn't rely on it.
@Conan_Kudo@fossrob@gbraad@adamw TBH, if you are not aiming for 1:1 binary reproducibility, then just rebuild it in OBS. You can either use build.opensuse.org, or use your own instance with interconnect to build.opensuse.org. Then create a new project, copy all packages from SUSE:SLE-15-SP$X:Update to your new project and enable building and publishing.
@Conan_Kudo@fossrob@gbraad@adamw Now getting updates into this setup will be a tad bit harder to pull of and that's one thing where it might actually be simpler on koji.
@Conan_Kudo@fossrob@gbraad@adamw But afaik no one ever really tried to create a Leap or SLES rebuild and actually distribute it, so this is all rather theoretical…
Also the elephant in the room is (as @fossrob) pointed out: Leap is already binary compatible with SLE and it's free and it has more packages. So why bother rebuilding it, just for the sake of rebuilding?
@gbraad both Leap and SLE are not only sharing the sources, they are also sharing the binary RPMs. That makes binary compatibility rather easy when they're the same thing 😉
@gbraad The majority of the packages are the same, the main difference are the branding packages and that Leap contains the community maintained packages which are not in SLE. So yes, it boils down to a slightly different package set.