On 10 April 2017 at 23:35, Lucas C. Villa Real <luca...@gobolinux.org> wrote: > On Mon, Apr 10, 2017 at 2:33 PM, Anshuman Aggarwal > <anshuman.aggar...@gmail.com> wrote: >> >> I have started pruning the PackageNames.txt file for a server install. >> Can we split this file into a say ServerPackageNames.txt and append >> the GUIPackageNames.txt and the ISO build script can be given an >> option to make either one? This will allow us to keep server and gui >> ISO builds around without double maintenance? >> >> Regards >> Anshuman >> > > To be fair, I wouldn't like to touch the installer right now. We're going to > have a complete rewrite of it very soon, now that our abstraction toolkit > (AbsTk) library has been ported to Lua. We'll likely want to go with a > different approach to the installation of remote packages instead of the > traditional "network install", too. > > Thanks, > Lucas >
I suggest that the new installer have multiple installation options for packages like minimal, server or at least GUI/No GUI (headless/virtual vs desktop/laptop use cases). Also does Gobo have the concept of meta packages where a recipe is only used to install dependencies automatically like Ubuntu-desktop etc? Even though the file system itself is the database of installed packages, it is very convenient to be able to just install/remove a whole set together without having to remember dependencies. I just went to the package list in GoboALFS and it was daunting for someone who doesn't which packages depend on which one, since gnu-linux is so inherently modular and has so many inter dependencies on installed packages. Thanks Anshuman _______________________________________________ gobolinux-users mailing list gobolinux-users@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
