How all this fits

Non release banter
Post Reply
M. Eerie
Black ninja
Black ninja
Posts: 58
Joined: 31 Aug 2017, 21:18
Distribution: APorteus BUDGIE x64

How all this fits

Post#1 by M. Eerie » 14 Feb 2018, 16:36

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!

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1162
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

How all this fits

Post#2 by ncmprhnsbl » 15 Feb 2018, 01:50

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..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
brokenman
Site Admin
Site Admin
Posts: 5750
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

How all this fits

Post#3 by brokenman » 15 Feb 2018, 13:28

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 do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply