Linked by Thom Holwerda on Mon 18th Aug 2008 23:33 UTC, submitted by Charles Wilson
Editorial GoboLinux is a distribution which sports a different file system structure than 'ordinary' Linux distributions. In order to remain compatible with the Filesystem Hierarchy Standard, symbolic links are used to map the GoboLinux tree to standard UNIX directories. A post in the GoboLinux forums suggested that it might be better to turn the concept around: retain the FHS, and then use symbolic links to map the GoboLinux tree on top of it. This sparked some interesting discussion. Read on for more details.
Thread beginning with comment 327350
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Good stuff
by hobgoblin on Tue 19th Aug 2008 14:27 UTC in reply to "Good stuff"
Member since:

referring to to sandboxes and such?

works ok for me.

however, the wiki should probably have some content removed or marked as no longer valid as it makes a single step install (if your dealing with a sane ./configure based source archive) into a multistep one.

basically its this:

MakeRecipe "app-name" "version-number" "url-to-source-archive"

then let the scripts chew on it for a bit and spit out a basic recipe.

then you go:

Compile "app-name"

if all goes well, you should be left with a working app, ready to be used.

as for multilib, if your thinking about having multiple versions of the same lib side by side then yes. i currently have two versions of QT installed.

one to support kde 3.5.x, the other to support the latest smplayer.

its a bit messy tho as one have to juggle SymlinkProgram a bit to get the correct lib version to be Default.

Reply Parent Score: 2

RE[2]: Good stuff
by zombie process on Thu 21st Aug 2008 12:57 in reply to "RE: Good stuff"
zombie process Member since:

Thanks for the heads up. I can't honestly recall what issues I was having, but they were real and there were forum posts about similar issues. I think they were in the middle of some major upgrade to the build system or something similar. Sorry if this is vague - I really can't remember what the problems were specifically. Dumb question/lazy alert: once the packages are compiled, is there anything that keeps track of what you've installed and what the deps were? I frequently compile my own packages, but I want something keep track of stuff for me - mundane crap like that is exactly what I think computers are *supposed* to do.

I think that what seems like an overall lack of traction to some is probably caused by the FS changes apparently being newbie-targeted while the OS itself is far closer to slackware or arch as far as management goes (at least when I was test driving it). It's hard to convince someone who knows the FHS well enough to get around efficiently that they should change, and it's hard to convince someone who demands (often quite vocally) that things must work w/o any elbow grease or clue-gain whatsoever that they should OMFG compile anything.

I'm interested to see where Gobo goes, though. I think it could be a real winner if it manages to sway some old heads and some new heads, and they can work together.

Reply Parent Score: 2

RE[3]: Good stuff
by hobgoblin on Thu 21st Aug 2008 14:09 in reply to "RE[2]: Good stuff"
hobgoblin Member since:

well a homemade recipe will show up in /Files/Compile/LocalRecipes, but beyond that there is not much that allows one to tell a homemade install from one found in the repository (that i know of at least).

and every versioned dir has a Resources subdir that among other things hold a dependencies file. this is autogenerated at end of a Compile if none exist before.

and the FS (or the distro in general) is not really newbie targeted. its more of a KISS (Keep It Simple, Stupid) design that happens to have some newbie friendly qualities (that is if one ever gets the precompiled packages to match the number of recipes).

Reply Parent Score: 2