On 27 July 2017 at 13:26, Robert Alexander <[email protected]> wrote: > Hello gobo-folks, > > Has anyone of you tried out the "Bash Subsystem on Windows" yet, > on Win10? > > https://blogs.msdn.microsoft.com/commandline/ > > It works for me fairly well so ar. > > My idea is to try and setup a "GoboLinux-like system" there. Then > I could use it to test stuff, including GoboLinux but also my > own scripts; on my todo list is to autogenerate all available > GoboLinux recipes in a valid way. > > Currently, ubuntu and opensuse work on Win10. I am using ubuntu as a "base > system", on a win10 laptop. Compiling works very well albeit it is slower > than on a "full" linux system from my experience. That is fine for me though > since I only use the laptop as a test system mostly. My main workhorse is > still an oldschool desktop computer. > > Since I do not really use apt-get, and I still consider the /Programs > hierarchy far superior to the FHS, wanting to have a GoboLinux > like layout seems logical (to me). My ruby scripts work fine > as well on that win10 machine, so I should be able to automate everything > as much as that is humanly possible. > > So without much further ado, to my questions: > > - If I wish to start or "bootstrap" a GoboLinux or a GoboLinux-like system, > using the "official" scripts, which variants from the gobolinux github area > should > I get first? And will this ultimately work or am I missing something here in > my > thought process? > > I had a look at the GoboLinux scripts at github: > > https://github.com/gobolinux > > I assume I need foremost these three: > > "Scripts" > > https://github.com/gobolinux/Scripts > > Also the: > > "Recipes" > > https://github.com/gobolinux/Recipes > > Probably also > > "Compile" > > https://github.com/gobolinux/Compile > > Aside from these three basic building blocks, do I need anything > else? Do I need the DevelScripts? Would BuildLiveCD help? > > And with which ones should I start or setup first? > > There is not a lot of documentation available e. g. at > https://github.com/gobolinux/Scripts but also lacking in > general, which I can understand to a large extent. My own > scripts do lack documentation too. Time constraints persist > for most everyone. :) > > I guess for me the most important part is the part where I can get things > to the point of "working" on a "GoboLinux-like setup", just in the > very same way as if it were a full/real GoboLinux setup.
For a GoboLinux-like setup, if you don't want to maintain the entire system, but use it to build and maintain your own packages, I think what you'd like to have is Rootless, which is an execution mode we used to have for Scripts and Compile that allowed them to run under any base prefix other than the root directory. So, for example, one could have /home/robert/Programs on Ubuntu, or /Users/robert/Programs on OSX and it even ran on Cygwin. As our user base dwindled over the years, we ended up deprecating the Rootless mode of running Scripts+Compile for one major reason: making recipes that are base-prefix-agnostic is often a lot of work. A lot of core programs expect to be installed under /usr. So, we started building programs targeting /usr and using a Union Filesystem to move files into their appropriate place under /Programs. That said, if you have a Linux system (or a sufficiently Linux-like system as the new Windows subsystem seems to be) then you could in theory add a /Programs directory in your root and use the GoboLinux infrastructure on top of an existing distro. On Windows the UnionFS sandboxing will certainly not work, but the rest could, especially if you set $goboIndex in the GoboPath file to something like /System/Index (and not /usr), and set variables like $PATH, $LD_LIBRARY_PATH, $C_INCLUDE_PATH and friends to point there as well. So, I'd say it should be possible but it would take a fair amount of tweaking. An alternative approach: To rebuild an entire GoboLinux /Programs from scratch, the place to look is https://github.com/gobolinux/GoboALFS — no idea how well that will work on the Windows subsystem, but I wouldn't rule out being surprised by it. You could try to run that and then see if you get to a point in which you have enough programs built such that you can chroot into the new root directory. > I can also help add information to the github-wiki so that this is > not ultimately lost in the mailing list archives, like 10 years old > archives such as "would you like to be a recipe committer" - > actually, some of the ancient discussions are nice to read years > lateron - nostalgia and such. > http://lists.gobolinux.org/pipermail/gobolinux-users/2007-July/thread.html > :D Oh boy :) > For anyone else interested in improving wiki-documentation by the > way, the link is at: > > https://github.com/gobolinux/Documentation/wiki Thank you for the initiative, let us know about your progress, and hit us up with any questions! -- Hisham _______________________________________________ gobolinux-users mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
