Re: Seting up a non-root installation

Thanks Lucas and mpb!

I think I have a better understanding of the structure of packages now.

It appears wiki.gobolinux.org is broken.  Is there any other source of
documentation, for example, for the recipe API?

Other parts of the website, in addition to many package mirrors, are also
broken.  Is this known?  Should I report these as I find them?


Anthony

On Thu, Oct 23, 2014 at 9:42 AM, Lucas C. Villa Real <[email protected]>
wrote:

> On Wed, Oct 22, 2014 at 11:56 PM, mpb <[email protected]> wrote:
>
>> On Wed, Oct 22, 2014 at 4:51 PM, Anthony Frachioni <[email protected]>
>> wrote:
>> > Hello GoboLinux!
>> >
>> > I've just found GoboLinux, and it appears to offer a useful way in
>> which to
>> > manage software in user space.  I am trying to build various things, and
>> > have a couple questions:
>> >
>> > -- First, my primary goal is to manage an assortment of free software
>> > installed on a machine running Ubuntu (and possibly others) to which I
>> do
>> > not have root access.  GoboLinux seems well suited to this task, am I
>> wrong
>> > in this assessment?
>>
>> I used Gobo Rootless in this manner.  This was over five years ago, I
>> think, so my information may be out of date.
>>
>> > -- Simply running InstallPackage without downloading the package
>> beforehand
>> > fails for all packages I've tried, presumably because the official
>> GoboLinux
>> > page is the only package mirror not down.  Is there a way to fix this?
>>
>> InstallPackage installs binary packages that are compiled to be used
>> inside Gobo Linux (ie, not inside Rootless).
>>
>> Inside Rootless, you want to use Compile and compile packages from source
>> code.
>>
>> > -- Any time I InstallPackage, I get the following message (even on
>> apparent
>> > success).  Maybe this isn't a problem, but it seems to suggest somebody
>> is
>> > trying to use root paths in a non-root installation.  Does it indicate a
>> > problem with my installation?
>> > /sbin/ldconfig.real: Can't create temporary cache file
>> /etc/ld.so.cache~:
>> > Permission denied
>> >
>> > -- GCC installs, but the resulting executable is broken.  It cannot find
>> > libgmp.so.3, which isn't there and is not created by installation of
>> the GMP
>> > package.  If I cheat a bit and soft-link libgmp.so.3 to libgmp.so.10
>> (this
>> > is probably a very bad idea anyway), I get the message:
>> > /usr/include/features.h:374:25: fatal error: sys/cdefs.h: No such file
>> or
>> > directory
>> > This sounds bad.  As I am unable to get a working C compiler in
>> Gobo-space,
>> > the Compile script does not work (though it does appear to succeed at
>> > finding recipes).  Is there any way to set the compiler used by Compile
>> to
>> > something else?
>>
>> Good luck with that.  I expect GCC has many dependencies, and may
>> require extra work to get it working inside Gobo Rootless.
>>
>> I would often run "apt-get build-dep <debian-package-name>" to install
>> all the Debian/Ubuntu provided dependencies and the run "Compile
>> <gobo-recipe-name>" to try to compile the package inside Rootless.
>>
>> I have not used Gobo Rootless in years.  Most recently, when I wanted
>> to use a new version of GCC, after trying several options (including
>> manually compiling the compiler - I was unsuccessful), I ended up just
>> setting up a VMs inside VirtualBox running Debian testing and/or
>> Debian unstable and working inside the VMs.
>>
>> Good luck!
>>
>>
> Greetings!
>
> As pointed out by Matthew, GoboLinux Rootless is probably your best bet
> here. You won't be able to install binary packages, but it will be possible
> to compile programs from the source code using our Compile tool. The steps
> below should bring you a working Rootless installation at your user's home
> directory:
>
> ### Begin ###
>
> if [ ! -d "$HOME/Programs/Scripts" -a ! -d "/Programs/Scripts" ]
> then
>    wget
> http://svn.gobolinux.org/tools/trunk/Scripts/bin/CreateRootlessEnvironment
>    cat CreateRootlessEnvironment | sed 's,make &&,make STATIC= \&\&,g' >
> tmp.old && mv tmp.old CreateRootlessEnvironment
>    chmod +x CreateRootlessEnvironment
>    ./CreateRootlessEnvironment
> fi
>
> source "$HOME/Programs/Rootless/Current/bin/StartRootless"
> source GoboPath
>
> if [ ! -e "$goboPrograms/Scripts/Current/bin/List" ]
> then
>    cd "$goboPrograms/Scripts/Current"
>    make -C src/ STATIC=
>    SymlinkProgram Scripts
>    cd -
> fi
>
> InstallPackage --no-dependencies Compile
> Compile --no-dependencies Mtail
>
> ### End ###
>
> It is recommended to change your user's shell to zsh (instead of bash) for
> a nicer experience.
>
> Once you have completed these steps, you are ready to build packages using
> Compile. It is worth noting that living with Rootless can be a little
> tricky. You will need to have some good idea about which packages you
> already have installed so that, when Compile tells you that a certain
> dependency is missing, you can safely tell it to skip building that
> dependency. I sometimes prefer to install dependencies through yum (because
> many times the host OS already has the required packages, except for
> development libraries and headers). For instance, I always ignore
> suggestions from Compile to build large and fundamental packages such as
> GCC, Glibc and Xorg.
>
> Hope this helps.
> Lucas
>
> _______________________________________________
> gobolinux-users mailing list
> [email protected]
> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
>
>

_______________________________________________
gobolinux-users mailing list
[email protected]
http://lists.gobolinux.org/mailman/listinfo/gobolinux-users