#6 lack of documentation for replicate the process without patches

[PICCORO Lenz McKAY]

i'm interesting in how are that build, what modifications are made to the system and how could that build without network connection.. where's the docs? please repo url no forums child links

why this work are not in sync as oficial projectin inside Devuan distribution team? are not secrect that devuan need some work

this project has come a long way since my last reviewed it a few years ago. (and also give opinion in the dev1 forum)

Debian has a big reason for the live build system, it can buil with right commands exact equal images of their oficial builds.. for any user that follow same process.. in any arch for any flavour.. that why i open thi issue!

[David Hare]

Thanks for your comments/questions. I note you authored VenenuX GNU/Linux (not tested here yet!) I will try to answer as well as possible.

ExeGNU builds are made from a custom bash script which (in stages) begins with debootstrap and ends with generation of the ISO image. Not because the script is superior to live-build (it is not and is simpler) but it does exactly what I want for clean and bloat-free i386 and amd64 builds.

The script (remaster_snapshot) is available in the Sourceforge page "experimental" section (GPL but use at your own risk). You can't build without a network connection (except if you have a complete, updated apt cache) and there are no docs! Please ask if you want more info.

ExeGNU builds are (among others, e.g. Refracta) technically 3rd party builds, which official Devuan cannot be expected to provide support for. Also ExeGNU uses Trinity Desktop Environment, only available via a 3rd party repo. TDE is not (yet at least) officially supported in Devuan.

The first ExeGNU images were produced after KDE3x was abandoned for the (not even comparable) KDE4. KDE3 was forked to Trinity Desktop Environment and still actively developed. ExeGNU switched from Debian to Devuan because I do not wish to support systemd. My support for Devuan and TDE goes back to their beginning.

There are (intentionally) no actual system modifications. ExeGNU is a bootstrapped Devuan base with TDE, some (useful but non-system-critical and removable) custom scripts, custom deb packages and custom defaults added.

Cheers,
David

[PICCORO Lenz McKAY]

this will be long long long.. ok i explain to you....

i compared package list amd64 vs i386 and also i noted that there's no arm build.. that's the first problem..

i already know why you use a custom script unless devuan tools or debian live build.. one of them are not installed extra packages and made specific configuratuions.. of course amont others reasons.. in my case i must made all "off-line - able" also

all of these are perfeclty made with upstream tools, but need expertise knowledge.. of course.. another reason..

so my intentions are (due Devuan are obtuse persons that always will have problems internally and does not sync collaboration with persons like you and much others) provide mos closes devuan trinity desktop made.. and venenux also of course but most close to devuan without customizatioins..

you have by example 4 own made packages for the customizations in the exe gnu live build.. by example the exegnu-installer, exegnu-trinity-themes and exegnu-userdefaults-trinity...

so i think it's better follow moste close the upstream tools to make a oficial derivative work and provide more easy way to reproduce exact images for all persons..

to make sense, amd64 build has a extra package named audacity-data that are not in the x86 flavour, but that again not are used by any other package due audacity are not provided in none of the flavours.. an error? X-D

puff.. yeah.. could be to much work to do.. but will be better to collaboration and uopstream help.. remenber that alone any work are more hard and heavy!