GoboLinux: A distro that redefines the entire filesystem hierarchy
gobolinux.org
gobolinux.org
It's not clear that GoboLinux entirely solves this issue but at first glance it looks like it's trying and the /Programs organization is pretty intuitive.
What's not appealing at all though is using a distro that doesn't have custom packages for all the software I'm using (aka is not Ubuntu or RedHat based). I'm not at all comfortable building from source--when I've tried it I've rarely been successful--and the prospect of further winnowing down my choices (from not just Linux-compatible software to software that however many GoboLinux users have uploaded to their Recipes directory) is, well, pretty intimidating.
On Windows, however, the only organized region would be that applications get a folder, but there's multiple potential locations (Program Files, Program Files (x86)), and they might also dump a bunch of things in various user-local folders, as well as the giant landfill that is C:\Windows. It lacks structure, to the point where there is even clones of UNIX structures in there (C:\Windows\System32\drivers\etc\hosts?!?).
Similarly, the Windows organization of %USERPROFILE%/AppData/Local/ , %USERPROFILE%/AppData/Local/Temp/ , and so forth has a parallel on Freedesktop operating systems.
* https://unix.stackexchange.com/a/313001/5132
And of course as indicated on this very page at https://news.ycombinator.com/item?id=14927512 and https://news.ycombinator.com/item?id=14926999, interference was not the reason for the creation of /usr .
People have also observed on this very page that far from being new-fangled, as it has been mischaracterized on this page, GoboLinux has been around and doing things like this for almost a decade and a half. (Of course, as NextSTEP and Windows NT 3.5 show, the idea is almost a decade and a half older than that, even.) It is interesting to note that slightly earlier than that, Daniel J. Bernstein, around the turn of the century, proposed a /package hierarchy (for package management without the need for conflict resolution) and a /command directory.
* http://cr.yp.to/slashpackage.html
* http://cr.yp.to/slashcommand.html
You seem to have missed that I did not complain about "Program Files" being nicely organized folders containing all relevant application data (although I am highly allergic to unnecessary capitalization and poor naming), nor say that Windows was the only platform with a mess, but rather complain that there are multiple such program locations (Program Files, Program Files (x86), and some applications install to user folders), that Program Files contain a bunch of entries for things aren't programs (helpers, things that installed elsewhere for stupid reasons, etc.), that AppData is a hidden mess, and that the Windows folder is a ghastly landfill that contains everything under the sky, including things that should have gone in the other locations (system applications, libraries, ...), things that didn't fit anywhere (most of whats in here), and even configuration files in UNIX directory structures (/c/windows/system32/drivers/etc/hosts). It's a disgusting mess in there that cannot by any meaning of the word be considered organized.
Note that I have not used Windows for at most 60 contiguous minutes for the past many years, so my memory may fail me.
* https://msdn.microsoft.com/en-gb/library/ms997548.aspx
* https://blogs.msdn.microsoft.com/oldnewthing/20110620-00/?p=...
* https://blogs.msdn.microsoft.com/oldnewthing/20120307-00/?p=...
And of course the windows directory being a subtree with everything that is part of the operating system, is exactly the same model that people have been adopting with the "/usr merge" from AT&T Unix System 5 Release 4 onwards, and only a "landfill" if one thinks having the operating system in its own single subtree off the root is a "ghastly" idea. The range of operating systems that have done this very thing over the years, with the likes of C:\DRDOS, C:\WINDOWS, C:\OS2, /System, /boot/system, and /usr, are really not for you in that case.
By the way, your description of priorities with / overriding /usr overriding /usr/local was as misleading as your idea about interference rather than the far more mundane and ordinary having a second disc. In fact, on systemd operating systems the default path is to search in the order /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin which is the opposite order to your description. FreeBSD nowadays uses a similar order, with _PATH_DEFPATH being /usr/bin:/bin , although _PATH_STDPATH is /usr/bin:/bin:/usr/sbin:/sbin . OpenBSD goes with /usr/bin:/bin:/usr/sbin:/sbin:/usr/X11R6/bin:/usr/local/bin for both.
The misleadingly simplistic and wrongly ordered /, /usr, /usr/local wasn't even the historical case, moreover. Back in the 1980s people had the likes of /usr/ucb, /usr/lbin, /usr/bin, /usr/5bin, and sometimes even /etc and /usr/etc on the search path. There were actually quite a lot of these. AT&T Unix System 5 Release 4 had them all under /usr in 1988.
/opt is alright. It's where you dump your tar ball and compile your custom stuff and place it under not to mix stuff up with package managed software. Not sure how people differentiate against /usr/local though.
I'm not particularly bothered about /bin vs /usr/bin, these days everything is in /usr/bin -- unless you are in an embedded scenario, and at that point everything is custom anyway.
The one location that doesn't make sense is /usr/sbin, which is hopefully being phased out.
Tbh the only thing I really miss is having ~/bin in PATH by default (and ~/lib, ~/share etc similarly picked up where necessary), since installing software in personal userspace is still pretty common in real multiuser environments; standardizing that would help, imho.
Not sure that will become standardized, it's a big security risk. Usually you want ~/bin to be at the front of your PATH so it takes priority, but the downside is... well that it takes priority. It's easy for someone to subvert the stuff in PATH because they only need your permissions.
Arch undid this, but did it the silly way by letting /bin be a symlink to /usr/bin. I would have preferred it the other way around.
Yeah, Fedora wants to move everything to /usr, last I heard. I personally think it's a stupid idea (/usr is just a vestige of Unix's early development and was never meant to be a permanent part of the Unix filesystem layout) and would prefer everything to be under /, but whatever.
"Not sure how people differentiate against /usr/local though."
/usr/local is typically reserved for stuff built from source. OpenBSD also uses it for things installed via the package manager.
/opt is a lot more freeform. Yeah, you can create an /opt/bin or /opt/lib or what have you, but the way I've seen it used (and the way I personally use it) is something closer to Program Files (so I'll have /opt/firefox or /opt/julia or whatever). A lot of commercial software packages will install to /opt in a similar manner.
/usr was originally where the user's files (everything but the OS) lived, but when they ran out of space they decided to just move OS stuff into it.
The whole "/bin is available on boot until /usr is mounted" story, which a classic form of post-rationalization, though it was presumably a useful distinction for a while.
[1] http://lists.busybox.net/pipermail/busybox/2010-December/074...
file-hierarchy(7) appears to be a more modern alternative.
(Cue complaints from users of a real UNIX about how GNU/Linux is such a cobbled together poorly documented hodgepodge...)
the more you know
That is an incredible little tidbit. I love finding out the answer to most of my questions is under my nose in the docs baked right in
Arch has what is called the Arch User Repository (AUR). It's a repository of recipes for building all kinds of software, and it's submitted and maintained by the users, not maintainers of the distro itself. Whenever there's a package missing in the official repositories, I almost always find it in the AUR. AUR has no binary builds---instead, you download files and scripts needed to build the software from source. You then run the makepkg utility, and you get a package you can install. (There are also helper programs which automate this whole process for you.) The result is that the package manager tracks the files properly, and you can keep track of which version you have, can remove the software cleanly, and update it whenever you like.
Today, when I'm at a Ubuntu box, it's a pain in the ass to install some less-known software. I can download the sources and then try to build, and I usually succeed, but not before I've figured out the right flags, prefixes, build-time and run-time dependencies, etc. I also get questions pertaining to this from my friends that have recently switched to Linux, and I don't really have a solution to offer. Yes, there are PPAs, but more often than not, PPAs are outdated and are binary-only, meaning you can't really review how the binary packages came about.
AUR really solves the problem nicely. I'd like to see such a concept in another, more beginner-friendly distribution, that I can then recommend to people around me who are considering making the switch.
The main one being that whole AUR thing: What happens if there isn't a recipe in there? For example - you want to install something which only has a binary, no source, and can't be (legally) redistributed; what then?
Well - to "install" the software, you basically have to go thru all of the steps to build your own recipe, noting down what you do manually, and eventually getting to the point where you have a script (or whatever) to install the software. Then, you undo all of your manual work, and run your arch package to do the real install. Tada - you now have a working package for that piece of software, and have spent potentially hours to get to that point.
As a bonus, you can't redistribute that recipe, because it is based around a binary blob that was purchased and you don't have the rights to redistribute it.
At least, that's how I interpreted it. I honestly don't recall what piece of software I wanted to use, but I think it may have been EagleCAD - which has a Linux port, but is binary only. I think it only has RPM and DEB packages, so to get it on arch, you'd have to build your own package.
It wasn't so much the fact that you had to do this, just that it wasn't an easy and straightforward process (from what I recall), and if you only need to do it once or twice, it would be pretty arduous. Maybe by now (haven't looked) they have some kind of package conversion tool, which would be a great addition.
Yeah, I wish there were AUR for Ubuntu
Coming from Linux and macOS to Windows this year, the Windows filesystem has been... well, one of the very confusing things. Although I understand the Linux fs is messy (and macOS improves a bit on that), I'm used to it and it makes sense.
OT, the only good bit I found is the Outlook directory, mail, calendar, Office experience (but that will not make me stick to Windows either).
> I generally have no idea where my config files are stored
rpm -qc <package_name>
> and can barely find where programs keep their data
rpm -ql <package_name>
>And then I download some software that doesn't install itself and I have to figure out where to put it...
Not sure if you mean source to be compiled or a package?
>The fact that this is all only sorta-kinda standardized between distributions
Distributions exist because people have their own opinions on the best way to do things. Pick one you like and learn it.
If your complaint is that this isn't all obvious then I wholeheartedly agree with you. But this is genuinely a simple case of you not RTFM.
UX design failures like this is the main reason why Linux can't get more than 3% on desktop.
It would be like when AOL allowed their users on the internet.
With viruses and other crap too.
On Arch pacman -Ql <package> shows me the equivalent of a /Program/<package>/ directory.
Installed packages are organized for the benefit of the runtime environment since the user should never have to interact with the data hierarchy, much like how Android has a Data/<program name>/<random stufF> share dir with the packages cached elsewhere.
The only real problem I have with the current standard FHS is how terribly named everything is. There are mechanical reasons why having all your libraries in /lib or all your binaries in /bin is necessary to the environment and linker.
You download tarballs into Programs and unpack and configure make install there, it 'just works'TM somehow, (I like this - sort of). I think 'Couldn't you create a script which creates a load of symlinks (for any distro), put it in a folder on your desktop?'
Okay,.. help me here - what problem are we trying to solve again? I like the nice view of the applications we have, but just thinking quite often packages have their own symlinks for like lib.so.2-->lib.so.3 will this have symlinks to symlinks to... so now thinking is it really worth the effort for a nice view of the applications? What else do I get?
As for what benefit this brings... One big one is that it makes it very easy to mix together programs installed via the package manager and programs you compiled from source by hand. There is no need for an alternate /use/local hierarchy. Similarly it it better at handling those situations where you might want to install multiple versions of some software. It can create different versions of that virtual root filesystem but with symlinks that point to different versions in each one. The end result is similar to what you would get with chroot and other "container" tech but in a quite elegant way.
That's the one thing I hate about package managers - if you need to install from source, the manager has no clue about it; in fact, you can have multiple versions installed - a new version "from source" and an old version from a real package via the manager! It's also possible for the manager to uninstall stuff it knows about - along with part of the stuff of the new version, depending on various things.
I ran into that earlier when I had to upgrade and munge my Ubuntu system to get TensorFlow to work properly with Python 3 and some other stuff and crap I forget about; long story short, I can no longer perform an upgrade to my system (I'm on 14.04 too!) - the tool b0rks hard when I try, and I honestly don't recall enough to return my system back to working status (I also had to install a major upgrade to gcc - which necessitated upgrades to other things, new manual symlinks, hours of swearing).
This was all needed for the Udacity Self-Driving Car Engineer Nanodegree because of their system requirements for code and such (had I been running 16.04, it would have been easier - most likely - but that was also fraught with potential issues, which is why I didn't pursue it). Looking back on things, I probably shoulda used a container or VM, or built a new machine, but I was pressed for time. I was assured in the beginning, before the class started, that what I had would work - like many things in the course, this wasn't true (I'm not saying they lied or misrepresented stuff - my cohort was only the second cohort from November, and so I am a part of the "guinea pig" crowd as they debug the new course - paying beta tester, if you will).
A system like Gobo might have been useful for this...
So maybe you are a die hard fan of old ways, but it clearly is a mess and not user friendly at all. Just look at why the LSB was created and more importantly, why nobody is following it 100%. If that does not seem like a problem to you I don't know what to tell you.
As for the root structure, they do mention in the article that it is optional. It can be turned off by disabling the kernel extension.
When Unix was invented, the concept of hierarchical filesystems wasn't new, notably Multics had a hierarchical filesystem, but there were conflicting visions. At the time, most other operating systems divided the filesystems between a number of top-level containers containing files, but no nested containers. IBM's contemporary time-sharing system, VM/370, supplied users with a set of top-level "virtual" drives each containing any number of files. There were no recursively nested directories.
The designers of Unix wanted a simple Operating System suitable for software development so they tended to implement an idea and then use it as much as practical in the OS design. Rather than have top-level containers like drives that contain folders that contain files, Unix just had directories and files (both implemented with the same on device structures called inodes). This combination of simple ideas fully generalized can be seen throughout Unix: multiple pathnames can point (link) to the same inode providing a form of aliasing for filenames, the api for files is generalized to include access to (possibly raw) devices so devices show up in the filesystem hierarchy, etc.
[/]
The top level directory has the name /, unlike other systems all filesystem pathnames start at this single point.
[/etc]
System configuration is found here. Most of these files are simple text files that may be edited by system administrators. In the past administrators might directly edit /etc/passwd to remove a user. Now, things are more complex, but there is still a backwards compatible /etc/passwd file (containing encrypted passwords, etc.).
[/bin and /sbin]
Unix, from the beginning was, like it's inspiration Multics, a multi-user system. Reconfiguring the system, for example to add a printer or drive, normally required running in single user mode at a privileged level. For this reason the programs needed by administrators running single user were segregated and placed in /bin. The rest of the system could be left offline, useful when working on the rest of the system.
As Unix grew, more and more utilities were added to /bin until it made sense to segregate it into those utilities needed when even a normal user might find themselves in single user mode vs a system administrator doing something dangerous. The super-user type programs now go in /sbin while the essential, but far less dangerous utilities go in /bin. Ordinary file copy is /bin/cp while the reboot command is /sbin/reboot. Some of the division look arbitrary to me, like /sbin/ping instead of /bin/ping, but there is probably logic behind it.
[/usr and /var]
Once booted up normally in multi-user mode, /usr contains system read-only content (for example, programs and libraries) and /var contains system content that is variable (like log files).
The /usr directory is large and subsequently divided into a number of second level directories.
[/usr/bin]
This is where the rest of the Unix "binaries" (i.e. programs) reside. So while ls (the list directory command) is /bin/ls the c compiler resides in /usr/bin and is /usr/bin/gcc.
[/usr/sbin]
Like the division between /bin and /sbin more administrative commands not necessary for single user mode (see /sbin) are placed in /usr/sbin. For example, the command /usr/sbin/setquota used to set disk quotas on users is in /usr/sbin and not in /usr/bin.
[/usr/lib]
This is where Unix supplied software development libraries go.
[/usr/include]
This is where Unix supplied (predominantly C and C++) include files are placed.
[/usr/share]
System documentation, the man pages, and spelling dictionaries are examples of the files found in /usr/share. They are read-only files used by the system under normal (multi-user) operation.
By now /usr/share is full of further subdivisions since many programs and systems need a place to put their read-only information. For example there is a /usr/share/cups for the Common Unix Printing System to store information about printers, etc.
[/usr/local]
System administrators may add additional local data and programs to their system. It make sense that these would be segregated from the rest of the files under /usr that come with Unix. The contents of /usr/local are local to the machine and are further subdivided into programs in /usr/local/bin and read-only data for these programs in /usr/local/share.
[/usr/X11...]
Once, one of the biggest subsystems in Unix was it's support for the graphical user interface known as the X window system. There were development libraries and include files, commands, man pages, and other executables. Rather than swamping the neat file hierarchy with these new files they were placed under a single subdirectory of /usr. You will probably not need to look at this very often.
[/home]
Users home directories are placed here; mine is /home/todd. Often /home is on a different physical partition so that it can be unmounted and a new version of the operating system can be installed without touching /home.
[/tmp]
Temporary files, for example that don't need to be backed up, are placed here.
[/mnt]
I've mentioned mounting and unmounting. Unix systems support a number of different filesystem formats, and devices can contain multiple filesystems (for example on distinct partitions). These filesystem become accessible once they are mounted into the hierarchy. Users need to temporarily (and now automatically) mount USB drives somewhere so that their files can be accessed via a pathname. In the past, users would just pick a directory to mount over. Now, it's traditional for temporary mounts to be placed in /mnt.
[/dev]
In Unix, low level access to devices is done through device drivers that support a number of file interfaces. Because they appear as special files they can be found under this directory. This is a convenience for programs because it makes naming and access to devices very similar to naming for ordinary files.
[Finding out more information about Unix and its hierarchy]
The Unix manual pages are a great resource. Originally, the manual was a physical book (I've still got a couple) divided into sections. Section 1 were the commands one might type on the command line. Now it is much easier to simply use the man command to access the exact same content. Use a terminal and enter "man ls", for example, to get all the information on the ls command to list directory contents. (You will be surprised at the number of options.)
When you aren't sure of the command's name try the command "apropos" followed by a word you'd like to find the man page for. Passwords are an important subject so "apropos password" on my system lists 47 different manual pages for information on passwords. I see one listed as "passwd(1)". The (1) means it's section one so its about a command named "passwd", the command for changing your password.
Here are the sections:
(1) Commands
(2) System calls
(3) Library functions
(4) Special files like device files
(5) File formats
(6) Recreations like games
(7) Misc info
(8) System admin and daemons
If I was looking for the format of the password file I would enter the section number 5 as the first argument to the man command: "man 5 passwd". This would show me the documentation for the password file, /etc/passwd.
Filesystem hierarchy manual page: "man 7 hier" or, since it is in only one section: "man hier". To find the name, "hier", of this man page one could have used the command "apropos filesystem".
I hope this helps; it's probably too long.
[1] https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
http://lists.busybox.net/pipermail/busybox/2010-December/074...
If you haven't tried it in the last year or two, then you might want to give it another try. Keep to some simple rules:
- Look for 'enable' toggles for particular software (for configuration.nix), rather than adding just the package. If it exists, use it; it wraps any extra configuration that's needed.
- Don't use nix-env. If you want a package installed temporarily, use nix-shell. Your system is probably single-user anyway, right? This way you can put configuration.nix in git.
- If you must use unpackaged software, then install and use steam-run. Despite the name, it's really just an Ubuntu-esque chroot. (...which duplicates the Steam runtime environment, yeah.)
Forcing people to build package recipes for everything they want to use is helpful, but not actually required. :)
There isn't a good story for doing declarative package management with user packages (nix-env isn't it), though there are a hundred hacks.
- It uses Scheme rather than Nix. Advantage Guix: Nix wasn't intended as a general-purpose language, and is only reluctantly letting itself be pushed therewards.
- It's philosophically pure. The package repository doesn't allow any kind of non-free software, whereas Nix allows it behind a global allow-unfree switch. Advantage: Nix?
- It's smaller. Perhaps as a result of the first two items, Guix has fewer developers and fewer packages.
Beyond that, they're basically the same design implemented two different ways. The Guix project is nice, and if NixOS wasn't around I'd use it. The communities have cordial relations, with a lot of overlap.
Guix uses the Nix daemon, which sets up the build environments, among other things. I would not call this "the primary Nix package management code".
The file structure should be efficient for the computer and can be abstract for the user as they want a icon on their desktop and not much more.
You do know it’s a hack because the original Unix computer was running out of space and they hadn’t invented Union mounts yet... right?
I find macOS paths atrocious (too long, too inconsistent, and derived completely outside of UNIX traditions and norms) and I certainly wouldn't want them on my Linux system.
Discussion of the usr move on Fedora: https://fedoraproject.org/wiki/Features/UsrMove
Folks can progress without throwing away decades of tradition and tribal knowledge.
The person I responded to said the current Linux pattern of "/bin", and "/usr/bin", and "/usr/local/bin", etc. is inefficient (whatever that means). I said I disagreed (as much as one can without really understanding what is efficient about the new scheme or inefficient about the old) and pointed to a change that Fedora has made in recent years that simplifies it somewhat and recognizes that systems have changed (and the way we boot them has changed).
I'm not saying it is more efficient, I'm saying it's not less efficient (again, whatever that means in this context, you'd have to ask the person above me that I was responding to). But, I do find "one application per directory" very messy. My package manager knows where everything is so I don't have to.
This may not be awful. I'm not saying it is bad. I'm saying, "if we're going to change everything about the way we install, manage, update, and use software on Linux", there'd better be a damned good reason for it. It must be a clear improvement. This does not strike me as a clear improvement. It's clever for the sake of clever, without any significant value.
So, tell me why I'd want this. (And, "it's like macOS" sure as heck aint sellin' it.)
I remember around 1999 some sysadmins would say, create your own packages from source stuff that you need. Given the current filesystem, permissions, etc. creating your own stuff is not for the faint of heart. So what you did was search the web in hopes somebody had done it for you.
Fast forward to recent times, if you had to do devops where PHP was involved in some way, you would have felt remi was a guy that should be receiving free beer. Explain why we have arrived to that sort of situations.
Luckily nowadays, the world seems to have centered around Ubuntu, from Docker to whatnot, which makes everybody target Ubuntu at least. But to this day, I'm still a very fond user of Gentoo, even if the compile everything from source approach is a bit crazy, and its latest reincarnation, Funtoo, precisely because it gives me a machine that has everything I need when the time comes to deal with "the package not in my package manager" TM.
I understand the pain that older packages sometimes cause, but I think the notion that we should throw away good package management in exchange for...I'm not sure what exactly you're suggesting this new scheme provides, is a good trade. Gentoo is not a realistic option for most situations where you need stability over some length of time.
I looked over GoboLinux, and I see they offer multiple versions of packages, and that's cool and all. There are repos that do the same for CentOS/RHEL; Software Collections Library is a very good one that is sponsored by Red Hat. And, there's stuff like Flatpak coming down the pike which allows packages to be bundled up in a container with everything it needs.
One could argue that GoboLinux foresaw these needs (it's been around since 2002, apparently) and came up with a partial solution to the problem. I can't argue with that. But, it was, IMHO, so partial that it wasn't worth the trade. I'm not sure containers-as-packages are worth the trade in some cases, either, but it seems inevitable. So, I'm embracing it in my own work. It's definitely got some advantages.
And, yes, Gentoo is crazy.
This split comes from the times when it was not uncommon for workstations to share installed programs using network filesystems.
Nowadays I prefer isolation though.
Or bad quality of keyboards in the past forcing use of super short commands/directory names?
This is also likely where the prompt character comes from, today we can do without it because terminal emulators remember the input and execute it once the current command is done but back then it actually prompted you to start typing.
Teleprinters is also where the word 'tty' (there are tty and tty with numbers in /dev that represent virtual terminals and you can play with them a bit if you know how) came from.
Hidden files starting with a dot was also a quirk of the ls reimplementation at the time of making filesystem hierarchical that was supposed to hide . and .. (current and parent dirs) but the check it did was for the first character being a dot, thus the concept of 'hidden files' was born.
See: https://plus.google.com/+RobPikeTheHuman/posts/R58WgWwN9jp
And either way it's quite arbitrary because almost all command names are still based on English that is a second language to many (including yours truly, but I'm not complaining, I find the usual unix shortcuts rather nice and intuitive most of the time and most of all - extremely quick to write, PowerShell makes me shudder and I had such big hopes for it).
Many concepts are also unique to unix/computers/low-level usage so any name will be non-intuitive. If you never encountered the concept of mounting a filesystem and don't know what an inode is then 'list inodes too' and 'list mounted filesystems' are no better to you than 'ls -i' and 'df'.
And someone who knows will prefer the latter, because it's that much quicker to type and harder to mistype.
What about /usr/bin? /sbin? I know the background but Plan9's overlay directories are a better alternative to PATH.
In theory one could have a variant of /Programs live under /usr or some such, and just aim the symlinks into the traditional FHS. But the Gobo people figured that if they were to build a distro from scratch (initial Gobolinux releases piggybacked on existing minimal distro installs) why not see how far one could go.
Unlike various other projects out there, Gobolinux plays nice with the FHS. There is no demand from them regarding how the rest of the Linux community should structure things.
What a nice logical system, I've been a Linux user for about 15 years but would definitely prefer this.
In current time, where we have more computing power and storage than we know what to do with it, we can allow computers to be inefficient for the sake of becoming easier to use.
As the initial installs of Unix bumped into problems, local solutions were found that was then documented and presented as gatherings or in newsletters.
But... how do I go about actually installing those programs? Web search and then git-clone / manual download? How are dependencies resolved? Admittedly I haven't read the documentation, just the overview.
On a related note, I feel like Arch struck a nice balance with pacman and AUR.
https://github.com/gobolinux/Scripts/tree/master/bin
https://github.com/gobolinux/Compile/tree/master/bin
A package in Gobolinux is basically a tar-ball of the versioned dir in /Programs.
So if a precompiled version is available in the Gobo repo (sadly fairly limited as there is not really any resources for a compile farm available), InstallPackage will fetch the latest from there, unpack it, and run SymlinkProgram to have /System/Index updated.
Inside each package or recipe there is a Resources directory, inside there are a few files that describe the program or recipe, and a list of dependencies. these are parsed before compile or install, and additional updates/installs suggested.
Compile is the recipe equivalent of InstallPackage. It will parse a recipe, check dependencies, and download the source from the included url. The compilation and install will then take place in a union mount overlaying /System/Index, redirecting writes to the target dir in /Programs. After that completes successfully, SymlinkProgram will again be run to update /System/Index.
If you want to make a new recipe, there is MakeRecipe. You give it a name, a version number and a url (though it can attempt to guess the first two from the tar-ball name if left blank), and it downloads the tar-ball, unpacks it, and sets up a basic recipe of the content is one of the tools it has built in support for. Mostly a recipe is a set of steps to make things compile, things like switches to pass to configure.
If you simply want to a newer version of an existing recipe, there is NewVersion. All you may need to feed it is the new version number, though it may need a url as well if the one from previous recipes are no longer valid.
One thing I've always thought would be ideal would be if either or both of the 2 Linux desktops that natively implement the idea of application-directories were top support Gobo app-dirs.
Those 2 are GNUstep:
... and the ROX Desktop:
http://rox.sourceforge.net/desktop/
GNUstep implements NeXTstep/macOS style app dirs: a top-level Appname.app folder with an OS X-like structure inside it.
ROX Desktop implements Acorn RISC OS-style app dirs, called
!Appname
... and containing a different but comparable layout.
What I wanted to do was create an "append only" "everything is installed" operating system on top of ipfs. Gobo, with it's ability to have multiple versions of each component in the same tree, seemed perfect for that. The idea being that you just run an executable right out of the ipfs mount.
I should give it another go to see how it has evolved.
While Links used a gobo unique set of directory names to house the symlinks, Index basically acts like /usr/local.
meaning that these days a compile is done pretty much as if one would do ./configure --prefix=/usr/local. But the install stage is captured by a union mount and the files transferred to their designated location in /Programs.
Sadly this change makes it that much harder to run Gobolinux in Rootless form out of a home dir or similar.
A small change like this is cool but pacman/aur leaves almost nothing to be desired for dealing with my programs. I do like the idea, but I would need to see a compelling philosophy for the __whole__ system.
Meaning that downloads from cpan or similar will be placed in a sub-directory of /Programs and managed just like any other Gobolinux package.
Right now perl, python, ruby, and lua are supported (afaik).
I've been sysadmining for a long time, and even I get lost in the old dir structure sometimes, I've just gotten good at the find command.
Never mind that Gobolinux do not even use Systemd.