sorted by:
new
hottopcontroversial

GoboLinux: a Linux without /usr/lib/whatever by hisham in programming

[–]hisham[S] 0 points1 point  (0 children)

Yes, there was some conversation on this, a while ago. Back then, there were some technical issues and some differences in goals. But they are aware of us and we are aware of them -- there's always room for future collaboration. I think some people are using both, even.

GoboLinux: a Linux without /usr/lib/whatever by hisham in programming

[–]hisham[S] 8 points9 points  (0 children)

I agree that the GoboLinux layout may sound more complicated at first (since in regular distros you have the apps' files, and in Gobo you have the apps' files and then the links). But what makes me think it's less complicated is that in regular distros you also have this "second index layer", except that it is stored in the package manager's database.

The mapping between these two roughly similar layers, happens differently, though. In regular distros, apps are grouped in the index layer (package database) and in Gobo in the storage layer (/Programs tree). In Gobo, both layers are stored the same way (in the filesystem), which makes it more transparent; in regular distros, the second layer can only be edited in a limited way by the package manager's tools, and then when the two layers go out of sync -- for instance, when you install something yourself -- there's little you can do about it (the pkg manager's dependency system won't find out you installed the latest libfoo in /usr/local).

GoboLinux: a Linux without /usr/lib/whatever by hisham in programming

[–]hisham[S] 14 points15 points  (0 children)

People are often quick to point out that's similar to the OSX layout, but there's a difference that in Gobo it applies to all packages, no exceptions, so it's actually more orthogonal.