User talk:Naib/RescueCD

Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 14:51, 5 November 2024 (UTC)
:: Your reply ~~~~

Systemrescuecd-5.3.2 Fork Process

Talk status

This discussion is still ongoing.

Step 1 is to recreate systemrescuecd-5.3.2 using the selected build environment, with everything at the same versions, just to check the build.

Step 2 is to update that, just as you would a Gentoo install.

Only after you can reproduce the starting point and update it is it time to think about additions and deletions to keep the resulting ISO CD size.

--NeddySeagoon (talk) 10:13, 5 March 2019 (UTC)

Two ways to go about this

1) Take SystemRescueCD-5.3.2 and do as you say

2) create a similar concept by building from the Gentoo MinimalCD

Part of me wants to go #2 route, but there is going to be more than just bootable CD with tools and thus #1 would be safer. It might be easier to unwind systemresucecd-5.3.2 than reproduce especially as it isn't that old.

--Naib (talk) 21:25, 5 March 2019 (UTC)

Hi! I did test a try to update the system root, but it seemed outdated and patched (OK, I would move it to ~arch, not a good idea). . I think starting from a new scratch + take their world file would be more useful.

--Xaviermiller (talk) 07:54, 6 March 2019 (UTC)

Project Members

I'm on board with this too - I've been working with catalyst on the releng stages, and wanted to customize a sysRescueCd with custom packages, only I never reached the point of unpicking the process used by rescuCD to build using catalyst (which it clearly does).

Perhaps we can get some specs together, and I can start some builds going (hoping to get a catalyst-buildbot setup asap to manage my other builds...).

LMK where you're at, and I'll pitch in where I can.

-- veremit (talk) 22:24, 12 April 2019 (UTC)

ISO image should be distributable

Note that the ISO image of version 5.3.2 was not distributable, mostly because of patent and trademark issues. That should be easy to fix by globally enabling the bindist use flag. See bug #682206 for details. --ulm (talk) 13:54, 18 April 2019 (UTC)

I'm assuming you mean re-distribute within the Gentoo licensing structures, because it's all over the internet as a 'release' from SysRescueCd with whatever arrangement are/not in place from upstream?! -- veremit (talk) 20:56, 18 April 2019 (UTC)

I mean legally redistributable. For example, freetype and openssl on the 5.3.2 CD both have patent encumbered code enabled. (So redistributing that release exposes oneself to a legal risk.) --ulm (talk) 04:59, 19 April 2019 (UTC)