[gobolinux-users] rootless - real_install

Dan theyranos at gmail.com
Wed Jun 14 23:44:41 GMT 2006 

Hi Marco,

I'll respond to your problems by number.

3) yes, you're right. That should be /usr/bin/install. Fixed the CVS  
version.

4) Huh... It does seem to be downloading a version of Scripts several  
versions old. I'm afraid to change it in CVS, though, because of my  
limited familiarity with Rootless. Can one of the devs take a look at  
this?

7) That sed error confused me for a long time too. I've been ignoring  
it for quite a while, and this is actually the second time I've gone  
to look for how to fix it. Fortunately, this time I figured it out.  
It's been fixed in CVS.

In your completion.bash file, change lines 28 through 30 to this:

[ -z "$BASH_COMPLETION" ] && declare -r BASH_COMPLETION="$ 
{goboPrefix}/System/Settings/completion.bash"
[ -z "$BASH_COMPLETION_DIR" ] && \
    declare -r BASH_COMPLETION_DIR="${goboPrefix}/System/Settings/ 
completion"


Then, in System/Settings/bashrc, move the line that says "source $ 
{goboPrefix}/System/Settings/completion.bash" down to line 66, after  
all those 'export' commands. Those two steps should fix the sed problem.

I haven't seen the cat error before. I just spent some time looking  
at the source trying to figure out what's causing it, but am drawing  
a blank.  Is there a / at the end of your $goboPrefix variable? If  
so, you may want to remove the extra / in Programs/Rootless/Current/ 
bin/StartRootless. I doubt that'll change anything, but it's worth a  
try.




> Hi Dan,
> I'm still experimenting problems with rootless installation; I try to
> explain what I'm doing and what I discovered:
>
> 1) I downloaded Scripts-2.3.1 from kundor.org
>
> 2) I made a fresh installation with the CreateRootlessEnviroment  
> script
> in that package and the process exits with the broken link to  
> "install"
> (I'm trying to install on an ubuntu box)
>
> 3) editing the script I noticed something that in my opinion coul be a
> bug. I copy here lines from 139 to 145
>
> if [ -e "/bin/install" ]
> then
> 	ln -sfn /bin/install ${goboPrefix}/Programs/Rootless/1.0/bin/ 
> real_install
> elif [ -e "/usr/bin/install" ]
> then
> 	ln -sfn /bin/install ${goboPrefix}/Programs/Rootless/1.0/bin/ 
> real_install
> else
>
> I think that the second link should be ln -sfn /usr/bin/install
>
> 4) another point is that in line 183 the version is hard coded on an
> older one
>
> version=2.2.1
>
> doesn't it should be 2.3.1, that is the version I'm installing?
>
> 5) I also overwrote the completion.bash scrip with the version you  
> sent
> me in a previous message, made the tar.bz2 and uploaded it on a my web
> server (changing obviously the address in the  
> CreateRootlessEnviroment).
>
> 6) I made a new fresh installation and the problem with the broken  
> link
> was solved!
>
> 7) Now I'm experimenting two more problems: this is an extract from  
> the messages I'm obtaining from the CreateRootlessEnviromen:
>
> ...
> ...
> Scripts/2.3.1/Resources/Dependencies
> Pre-linking Scripts...
>
> sed: impossibile leggere /etc/completion.bash: Nessun file o directory
> cat: /home/gobolinux/gobolinux//System/Links/Environment/*: Nessun  
> file o directory
>
> Linking Scripts...
> SymlinkProgram: Symlinking Scripts 2.3.1.
> SymlinkProgram: Symlinking global settings...
> ...
> ...
>
> I found the problem is in the bashrc script at line 9 for the first  
> error
>
> source ${goboPrefix}/System/Settings/completion.bash
>
> and at line 74
>
> source "$envcachefile"
>
> for the second (both with the source command...).
>
> Any idea how to solve them?
>
> Thank you
>
> Marco
>
>
>
> Dan ha scritto:
>> If the problems you're having with Compile are similar to the ones  
>> I was having (getting prompted for a sudo password all the time),  
>> you can fix them by replacing Programs/Scripts/Current/Functions/ 
>> GoboLinux with the latest CVS version.
>> http://cvs.savannah.gnu.org/viewcvs/*checkout*/tools/Scripts/ 
>> Functions/GoboLinux?rev=1.15&root=goboscripts Forgot to tell you  
>> when that was fixed. Sorry.
>>> Hi Dan,
>>> nothing to do: I tried with a new fresh installation using the  
>>> last CreateRootlessEnviroment version of the new Scripts release  
>>> but the result is the same as before. The installation has been  
>>> interrupted. I fixed it with the completion.bash and repaired the  
>>> broken link (real_install) but I'm experimenting problems using  
>>> CompileProgram.
>>> I will wait for your patches.
>>>
>>> Marco
>>>
>>> Dan ha scritto:
>>>> Hi,
>>>> I'm sorry you're having so much trouble with Rootless. I  
>>>> installed it on a university machine at the same time you did to  
>>>> test that file I sent, and I've noticed a couple of problems  
>>>> myself, which I'm going to try to track down and fix in the next  
>>>> couple of days.
>>>> The real_install link needs to point to wherever the 'install'  
>>>> binary on your host machine is. The following commands should  
>>>> fix it:
>>>> cd Programs/Rootless/1.0/bin
>>>> ln -fs "`which install`" real_install
>>>> Although, the other problems I've noticed (which are probably  
>>>> going to take me a while to find) are actually in one of the  
>>>> dependencies of Compile itself, rather than  
>>>> CreateRootlessEnvironment, so it's possible that even with that  
>>>> link corrected, you'll still have some difficulty getting  
>>>> Compile to work properly.
>>>> There's been a new version of the Gobo scripts released since  
>>>> your last message, so you may also have more luck if you remove  
>>>> the gobo line from your .bash_profile, rm the folder, and just  
>>>> reinstall rootless from scratch using a fresh copy of the  
>>>> CreateRootlessEnvironment script from the website.
>>>> I hope this helps. Let us know if anything else goes wrong.
>>>> Dan
>>>>> Hi all,
>>>>> I installed few days ago gobolinux in RootLess mode.
>>>>> I obtained an error during the installation: Dan sent me a new  
>>>>> version of a file (completion.bash) to overwrite to the one  
>>>>> generated by the CreateRootlessEnviroment and after re-running  
>>>>> the script everything went fine. At least, this is what it  
>>>>> seemed to me... During my first attempts to compile something,  
>>>>> I obtained errors from CompileProgram when it try to call the  
>>>>> real_install command.
>>>>> Now I recognize that in Programs/Rootless/1.0/bin there is a  
>>>>> broken link real_install to /bin/install: may be this is  
>>>>> because of the interruption during the CreateRootlessEnviroment  
>>>>> execution?
>>>>>
>>>>> Can I find somewhere a CreateRootlessEnviroment script working  
>>>>> properly?
>>>>>
>>>>> Thank you
>>>>>
>>>>> Marco
>>>>> _______________________________________________
>>>>> gobolinux-users mailing list
>>>>> gobolinux-users at lists.gobolinux.org
>>>>> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
>>>> _______________________________________________
>>>> gobolinux-users mailing list
>>>> gobolinux-users at lists.gobolinux.org
>>>> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
>>>
>>> _______________________________________________
>>> gobolinux-users mailing list
>>> gobolinux-users at lists.gobolinux.org
>>> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
>> _______________________________________________
>> gobolinux-users mailing list
>> gobolinux-users at lists.gobolinux.org
>> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
>
>
> _______________________________________________
> gobolinux-users mailing list
> gobolinux-users at lists.gobolinux.org
> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users

More information about the gobolinux-users mailing list