Thread: [Bashburn-info] I changed the Install.sh script.
Brought to you by:
bashburn
Menu
▾
▴
bashburn-info
|
From: Steven W. O. <st...@sy...> - 2008-09-14 21:37:51
|
Usage: Install.sh [ --prefix dir ] [ --uninstall ] [ --help ] --prefix will allow the user to specify the prefix directory where BashBurn will be installed or uninstalled. The default is $defprefix. The support files will go into \$dir/lib/BashBurn/lib and the program(s) will be in \$dir/bin I recommend removing the old stuff just to reduce clutter (and confusion). You can use --prefix in conjunction with --uninstall if you put it in a non-default location. Questions anyone? BTW, this will be useful as we go forward WRT the localization stuff. -- Time flies like the wind. Fruit flies like a banana. Stranger things have .0. happened but none stranger than this. Does your driver's license say Organ ..0 Donor?Black holes are where God divided by zero. Listen to me! We are all- 000 individuals! What if this weren't a hypothetical question? steveo at syslang.net |
|
From: Steven W. O. <st...@sy...> - 2008-09-15 01:43:58
|
On Sunday, Sep 14th 2008 at 17:37 -0000, quoth Steven W. Orr: =>Usage: => Install.sh [ --prefix dir ] [ --uninstall ] [ --help ] => =>--prefix will allow the user to specify the prefix directory =>where BashBurn will be installed or uninstalled. =>The default is $defprefix. The support files will go =>into \$dir/lib/BashBurn/lib and the program(s) will be in \$dir/bin => =>I recommend removing the old stuff just to reduce clutter (and confusion). => =>You can use --prefix in conjunction with --uninstall if you put it in a =>non-default location. => =>Questions anyone? => =>BTW, this will be useful as we go forward WRT the localization stuff. Sorry, I just wasn't satisfied with it. Instead of some home-brew options parsing, I switched it to use getopt. So now we support both short and long options. Much more betterer. Usage: $0 [OPTIONS] -p, --prefix=dir -u, --uninstall -h, --help --prefix will allow the user to specify the prefix directory where BashBurn will be installed or uninstalled. The default is $defprefix. The support files will go into \$dir/lib/BashBurn/lib and the program(s) will be in \$dir/bin --uninstall will remove all of the BashBurn files from your system based on its knowledge of what prefix is. --help This message -- steveo at syslang dot net TMMP1 http://frambors.syslang.net/ Do you have neighbors who are not frambors? Steve Orr Who should we vote for? http://steveo.syslang.net/electionrec-2008.5/ |
|
From: Nick W. <ni...@uk...> - 2008-09-15 07:47:50
|
On Sun, 14 Sep 2008 21:44:01 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > On Sunday, Sep 14th 2008 at 17:37 -0000, quoth Steven W. Orr: > > =>Usage: > => Install.sh [ --prefix dir ] [ --uninstall ] [ --help ] > => > =>--prefix will allow the user to specify the prefix directory > =>where BashBurn will be installed or uninstalled. > =>The default is $defprefix. The support files will go > =>into \$dir/lib/BashBurn/lib and the program(s) will be in \$dir/bin > => > =>I recommend removing the old stuff just to reduce clutter (and > confusion). => > =>You can use --prefix in conjunction with --uninstall if you put it > in a =>non-default location. > => > =>Questions anyone? > => > =>BTW, this will be useful as we go forward WRT the localization > stuff. > > Sorry, I just wasn't satisfied with it. Instead of some home-brew > options parsing, I switched it to use getopt. So now we support both > short and long options. Much more betterer. > > Usage: > $0 [OPTIONS] > > -p, --prefix=dir > -u, --uninstall > -h, --help > > --prefix will allow the user to specify the prefix directory > where BashBurn will be installed or uninstalled. > The default is $defprefix. The support files will go > into \$dir/lib/BashBurn/lib and the program(s) will be in \$dir/bin > > --uninstall will remove all of the BashBurn files from your system > based on its knowledge of what prefix is. > > --help This message Steve, You are altering RELEASE tree, not trunk. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@uk...> - 2008-09-15 07:54:01
|
On Sun, 14 Sep 2008 21:44:01 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > On Sunday, Sep 14th 2008 at 17:37 -0000, quoth Steven W. Orr: > > =>Usage: > => Install.sh [ --prefix dir ] [ --uninstall ] [ --help ] > => > =>--prefix will allow the user to specify the prefix directory > =>where BashBurn will be installed or uninstalled. > =>The default is $defprefix. The support files will go > =>into \$dir/lib/BashBurn/lib and the program(s) will be in \$dir/bin > => > =>I recommend removing the old stuff just to reduce clutter (and > confusion). => > =>You can use --prefix in conjunction with --uninstall if you put it > in a =>non-default location. > => > =>Questions anyone? > => > =>BTW, this will be useful as we go forward WRT the localization > stuff. > > Sorry, I just wasn't satisfied with it. Instead of some home-brew > options parsing, I switched it to use getopt. So now we support both > short and long options. Much more betterer. > > Usage: > $0 [OPTIONS] > > -p, --prefix=dir > -u, --uninstall > -h, --help > > --prefix will allow the user to specify the prefix directory > where BashBurn will be installed or uninstalled. > The default is $defprefix. The support files will go > into \$dir/lib/BashBurn/lib and the program(s) will be in \$dir/bin > > --uninstall will remove all of the BashBurn files from your system > based on its knowledge of what prefix is. > > --help This message > > OK, I can't get this to work at all. If I use no options, it tries to install in default location with no questions asked, and as I am not root... Second, if I use -h or --help - error, too many options. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@uk...> - 2008-09-15 08:39:00
|
On Mon, 15 Sep 2008 08:54:09 +0100 Nick Warne <ni...@uk...> wrote: > On Sun, 14 Sep 2008 21:44:01 -0400 (EDT) > "Steven W. Orr" <st...@sy...> wrote: > > > On Sunday, Sep 14th 2008 at 17:37 -0000, quoth Steven W. Orr: > > > > =>Usage: > > => Install.sh [ --prefix dir ] [ --uninstall ] [ --help ] > > => > > =>--prefix will allow the user to specify the prefix directory > > =>where BashBurn will be installed or uninstalled. > > =>The default is $defprefix. The support files will go > > =>into \$dir/lib/BashBurn/lib and the program(s) will be in > > \$dir/bin => > > =>I recommend removing the old stuff just to reduce clutter (and > > confusion). => > > =>You can use --prefix in conjunction with --uninstall if you put it > > in a =>non-default location. > > => > > =>Questions anyone? > > => > > =>BTW, this will be useful as we go forward WRT the localization > > stuff. > > > > Sorry, I just wasn't satisfied with it. Instead of some home-brew > > options parsing, I switched it to use getopt. So now we support both > > short and long options. Much more betterer. > > > > Usage: > > $0 [OPTIONS] > > > > -p, --prefix=dir > > -u, --uninstall > > -h, --help > > > > --prefix will allow the user to specify the prefix directory > > where BashBurn will be installed or uninstalled. > > The default is $defprefix. The support files will go > > into \$dir/lib/BashBurn/lib and the program(s) will be in \$dir/bin > > > > --uninstall will remove all of the BashBurn files from your system > > based on its knowledge of what prefix is. > > > > --help This message > > > > > > OK, I can't get this to work at all. If I use no options, it tries to > install in default location with no questions asked, and as I am not > root... > > Second, if I use -h or --help - error, too many options. > > Nick OK, I can get it to install, but specifying my home directory, I get this as installation path - which in not right, I feel: /home/nick/bashburn/lib/Bashburn/lib/ Nick -- Free Software Foundation Associate Member 5508 |
|
From: Steven W. O. <st...@sy...> - 2008-09-15 12:19:50
|
On Monday, Sep 15th 2008 at 04:39 -0000, quoth Nick Warne: =>On Mon, 15 Sep 2008 08:54:09 +0100 =>Nick Warne <ni...@uk...> wrote: => =>> On Sun, 14 Sep 2008 21:44:01 -0400 (EDT) =>> "Steven W. Orr" <st...@sy...> wrote: =>> =>> > On Sunday, Sep 14th 2008 at 17:37 -0000, quoth Steven W. Orr: =>> > =>> > =>Usage: =>> > => Install.sh [ --prefix dir ] [ --uninstall ] [ --help ] =>> > => =>> > =>--prefix will allow the user to specify the prefix directory =>> > =>where BashBurn will be installed or uninstalled. =>> > =>The default is $defprefix. The support files will go =>> > =>into \$dir/lib/BashBurn/lib and the program(s) will be in =>> > \$dir/bin => =>> > =>I recommend removing the old stuff just to reduce clutter (and =>> > confusion). => =>> > =>You can use --prefix in conjunction with --uninstall if you put it =>> > in a =>non-default location. =>> > => =>> > =>Questions anyone? =>> > => =>> > =>BTW, this will be useful as we go forward WRT the localization =>> > stuff. =>> > =>> > Sorry, I just wasn't satisfied with it. Instead of some home-brew =>> > options parsing, I switched it to use getopt. So now we support both =>> > short and long options. Much more betterer. =>> > =>> > Usage: =>> > $0 [OPTIONS] =>> > =>> > -p, --prefix=dir =>> > -u, --uninstall =>> > -h, --help =>> > =>> > --prefix will allow the user to specify the prefix directory =>> > where BashBurn will be installed or uninstalled. =>> > The default is $defprefix. The support files will go =>> > into \$dir/lib/BashBurn/lib and the program(s) will be in \$dir/bin =>> > =>> > --uninstall will remove all of the BashBurn files from your system =>> > based on its knowledge of what prefix is. =>> > =>> > --help This message =>> > =>> > =>> =>> OK, I can't get this to work at all. If I use no options, it tries to =>> install in default location with no questions asked, and as I am not =>> root... =>> =>> Second, if I use -h or --help - error, too many options. =>> =>> Nick => =>OK, I can get it to install, but specifying my home directory, I get =>this as installation path - which in not right, I feel: => =>/home/nick/bashburn/lib/Bashburn/lib/ => =>Nick I just checked. If you say ./Install.sh --prefix=$HOME then it will try to install in /home/nick/bin and /home/nick/lib/Bashburn/lib not /home/nick/bashburn/lib/Bashburn/lib The problem is that it tries to set ownership to root which is not allowed. I just fixed that too so it only runs chown if you're root. 542 -- steveo at syslang dot net TMMP1 http://frambors.syslang.net/ Do you have neighbors who are not frambors? Steve Orr Who should we vote for? http://steveo.syslang.net/electionrec-2008.5/ |
|
From: Steven W. O. <st...@sy...> - 2008-09-15 14:00:09
|
On Monday, Sep 15th 2008 at 03:47 -0000, quoth Nick Warne: =>Steve, => =>You are altering RELEASE tree, not trunk. => =>Nick Nick, should I have made those changes in trunk? I thought we were doing the localization stuff there. Also, I suppose I should merge the Install changes to truck -- steveo at syslang dot net TMMP1 http://frambors.syslang.net/ Do you have neighbors who are not frambors? Steve Orr Who should we vote for? http://steveo.syslang.net/electionrec-2008.5/ |
|
From: Nick W. <ni...@uk...> - 2008-09-15 14:01:12
|
On Mon, 15 Sep 2008 08:19:57 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > I just checked. If you say > > ./Install.sh --prefix=$HOME > > then it will try to install in > /home/nick/bin > and > /home/nick/lib/Bashburn/lib > not > /home/nick/bashburn/lib/Bashburn/lib > > > > > The problem is that it tries to set ownership to root which is not > allowed. I just fixed that too so it only runs chown if you're root. No, you get me wrong. If I use --prefix=/home/nick/bashburn I expect to see: /home/nick/bashburn/lib /home/nick/bashburn/bin etc. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@uk...> - 2008-09-15 14:14:42
|
On Mon, 15 Sep 2008 15:01:21 +0100 Nick Warne <ni...@uk...> wrote: > On Mon, 15 Sep 2008 08:19:57 -0400 (EDT) > "Steven W. Orr" <st...@sy...> wrote: > > > > I just checked. If you say > > > > ./Install.sh --prefix=$HOME > > > > then it will try to install in > > /home/nick/bin > > and > > /home/nick/lib/Bashburn/lib > > not > > /home/nick/bashburn/lib/Bashburn/lib > > > > > > > > > > The problem is that it tries to set ownership to root which is not > > allowed. I just fixed that too so it only runs chown if you're root. > > No, you get me wrong. > > If I use --prefix=/home/nick/bashburn > > I expect to see: > > /home/nick/bashburn/lib > > /home/nick/bashburn/bin > > etc. > > Nick More on this. sudo ./Install.sh --prefix=/opt/ Installation script for BashBurn Directory prefix has been set to /opt/ Installing files...[DONE] Creating symlink...ln: creating symbolic link `/opt//bin/bashburn': No such file or directory Can not create symlink ls /opt/lib/Bashburn/lib/ BashBurn.sh CREDITS FAQ INSTALL TODO config/ func/ menus/ COPYING ChangeLog HOWTO README burning/ convert/ lang/ misc/ It's bunging a top level 'lib' and 'bin' from somewhere. Surely it should install to <--prefix=<dest>>BashBurn directory? Nick -- Free Software Foundation Associate Member 5508 |
|
From: Nick W. <ni...@uk...> - 2008-09-15 14:04:35
|
On Mon, 15 Sep 2008 10:00:17 -0400 (EDT) "Steven W. Orr" <st...@sy...> wrote: > On Monday, Sep 15th 2008 at 03:47 -0000, quoth Nick Warne: > > =>Steve, > => > =>You are altering RELEASE tree, not trunk. > => > =>Nick > > Nick, should I have made those changes in trunk? I thought we were > doing the localization stuff there. > > Also, I suppose I should merge the Install changes to truck Yes, my impression was we work on trunk and Anders pushes through stuff that is tested/known to work OK to release branch. release is for stable code, not new code. I think... Nick -- Free Software Foundation Associate Member 5508 |
|
From: Steven W. O. <st...@sy...> - 2008-09-15 15:21:26
|
On Monday, Sep 15th 2008 at 10:04 -0000, quoth Nick Warne: =>On Mon, 15 Sep 2008 10:00:17 -0400 (EDT) =>"Steven W. Orr" <st...@sy...> wrote: => =>> On Monday, Sep 15th 2008 at 03:47 -0000, quoth Nick Warne: =>> =>> =>Steve, =>> => =>> =>You are altering RELEASE tree, not trunk. =>> => =>> =>Nick =>> =>> Nick, should I have made those changes in trunk? I thought we were =>> doing the localization stuff there. =>> =>> Also, I suppose I should merge the Install changes to truck => => =>Yes, my impression was we work on trunk and Anders pushes through stuff =>that is tested/known to work OK to release branch. release is for =>stable code, not new code. => =>I think... I will leave 3.0 alone and merge into trunk. Sorry. -- steveo at syslang dot net TMMP1 http://frambors.syslang.net/ Do you have neighbors who are not frambors? Steve Orr Who should we vote for? http://steveo.syslang.net/electionrec-2008.5/ |
Thanks for helping keep SourceForge clean.
X