Page 1 of 1

How all this fits

Posted: 14 Feb 2018, 16:36
by M. Eerie
I wonder how all this fits. I mean, we have Porteus Arch based, and Porteus Slack based (openrc). We have also @neko Archlinux packages manager (systemd), and other development toos he made available to everyone. Each one built from different concepts, and yet I imagine that much of the code will be reusable.

Question: Would'n it be a good idea to integrate all this into common tools to ease the development. I feel we are so close now...

I mean: Here --> viewtopic.php?p=61950#p61950 we have a census of packages to be included in every "base module". Also, I've been digging at neko's builds and see what packages he's including to build different desktops/environments.

What about keep a common+minimal list of these packages allowing everyone to build their own flavour? A minimal set of proved working base packages.

From there, a standarized and categorized repo should be easier to maintain and be contributed (I think).

Cheers!

How all this fits

Posted: 15 Feb 2018, 01:50
by ncmprhnsbl
some corrections/clarifications:
M. Eerie wrote:
14 Feb 2018, 16:36
I mean, we have Porteus Arch based, and Porteus Slack based (openrc).
that's Porteus Arch/Artix based(openrc) and Porteus Slack based(sysvinit)
M. Eerie wrote:
14 Feb 2018, 16:36
Each one built from different concepts, and yet I imagine that much of the code will be reusable.
well the basic porteus concept is the same: modules loop mounted via AUFS, live and/or frugally installed ..
Slackware, Arch/Artix and Arch are somewhat different in these areas: init/service management, filesystem structure, and package management...
M. Eerie wrote:
14 Feb 2018, 16:36
I mean: Here --> viewtopic.php?p=61950#p61950 we have a census of packages to be included in every "base module".
those lists are only the packages that were recently updated..
with nemesis the full list(s) are somewhat subject to change. eg. in the next update(coming) a bunch of *proto packages will be replaced by one xproto package..
see here: [How to] manually upgrade 3.5 base modules for an idea of the update process..
what's currently installed (in each module) can easily be found in:
nemesis/arch: /mnt/live/memory/images/<module>.xzm/var/lib/pacman/local/
slackware: /mnt/live/memory/images/<module>.xzm/var/log/packages
M. Eerie wrote:
14 Feb 2018, 16:36
What about keep a common+minimal list of these packages allowing everyone to build their own flavour? A minimal set of proved working base packages.
brokenman has build scripts(for slackware porteus) kicking around, i think he will release them once porteus 4.0 is finalised..

How all this fits

Posted: 15 Feb 2018, 13:28
by brokenman
When I first started nemesis the idea was to ease the workload and create a Porteus with a much wider pasture of packages available. There were questions as to what would happen to slackware based Porteus. I decided to create a slackware-current version of Porteus that could be updated easily so as to future proof it and then get back to developing nemesis.

The team here continued to maintain nemesis under various names and with slight modifications. The plan is still the same.

How all this fits

Posted: 18 Feb 2018, 09:49
by M. Eerie
ncmprhnsbl, I really appreciate your clarifications. Thank you for pointing them out.
brokenman wrote:
15 Feb 2018, 13:28
The plan is still the same.
Since Porteus Nemesis came to life it's been a while... By now, the Arch user base has grow and I think is growing faster every day. We should expect some more attraction and Porteus Nemesis would be a fine candidate to fill the gap for a migratory pendrive... ;) :whistling:

How all this fits

Posted: 18 Feb 2018, 14:32
by brokenman
M. Eerie wrote:
18 Feb 2018, 09:49
Since Porteus Nemesis came to life it's been a while...
Yes it has, and the noise about systemd has even faded a bit.

How all this fits

Posted: 20 Feb 2018, 01:25
by Tonio
brokenman wrote:
18 Feb 2018, 14:32
Yes it has, and the noise about systemd has even faded a bit.
Nope! Still here and hate systemd! Do not care for it and would bypass it as long as I can. We luckily have the BSDs, Void, Slackware, CRUX, and others who have avoided it and still do! My nephew does not care about systemd, I did not mind it at first, but I see what it is doing I do not like it. It reminds me of a girl that we invited to a party. We just wanted to have a good time, then she started serving food, and told us not to drink this or that, she started taking over all the things, which food we should eat, who to invite and who not to invite. What to drink and what not to drink. In the end, some of my friends and I left the party because she took over everything in our lives. It reminded me of systemd. It took over networking, it took over networkmanager, elogind, ... and other stuff. It wants to control everything. The noise might not appear to be there, but it does not excuse it from being hated by several members of the community.

How all this fits

Posted: 20 Feb 2018, 02:21
by ncmprhnsbl
Nemesis. at this point in time is "systemd free", using openrc for init and service management(and eudev and elogind)
provided by the Artix project, who package an alternate 'core' repository of Arch...

How all this fits

Posted: 16 Nov 2018, 22:05
by wread
Wao! after so a strong opinion of Linus Torvals, I'd never even take a look at systemd... :shock:

How all this fits

Posted: 17 Nov 2018, 00:39
by Ed_P
Do note the opinion was expressed 4 1/2 yrs ago.