bashburn-info — BashBurn mailing list

[Bashburn-info] From Nick: Fw: A few issues (fwd)

[Steven W. O. <st...@sy...>]

-- 
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/

---------- Forwarded message ----------
Date: Sat, 20 Sep 2008 05:24:38
From: Nick Warne <ni...@uk...>
To: Steven W. Orr <st...@sy...>
Subject: Fw: A few issues

Steve,

I am getting a funny issue with this list - my ISP IMAP server is
trashing the mails I send to the list, so can you forward this on to
the list please :-)

Nick

Begin forwarded message:

Date: Sat, 20 Sep 2008 10:17:25 +0100
From: Nick Warne <ni...@uk...>
To: bas...@li...
Subject: A few issues



If you go to 5) Configuration, and select the 'author' option (No. 8),
you cannot enter an email@address - the value gets 'chomped' at the '@'.

I had a brief look at the above, but can't see where it goes wrong.

Secondly, for Anders perhaps.

On the new branches, if I do an 'svn log', I can only see log history
for since the new branches was formed?  Ideas how to get the full
history log back?

Lastly, I posted a message to the board yesterday that has not arrived
(yet). I had an issue with the installation, but this is now solved - I
had to delete my .bashburnrc file, and then all was well again.  So
ignore this post if it arrives on the slow train.


Nick
-- 
Free Software Foundation Associate Member 5508

-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] A few issues

[Nick W. <ni...@uk...>]

If you go to 5) Configuration, and select the 'author' option (No. 8),
you cannot enter an email@address - the value gets 'chomped' at the '@'.

I had a brief look at the above, but can't see where it goes wrong.

Secondly, for Anders perhaps.

On the new branches, if I do an 'svn log', I can only see log history
for since the new branches was formed?  Ideas how to get the full
history log back?

Lastly, I posted a message to the board yesterday that has not arrived
(yet). I had an issue with the installation, but this is now solved - I
had to delete my .bashburnrc file, and then all was well again.  So
ignore this post if it arrives on the slow train.


Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] I just checked in the history games.

[Steven W. O. <st...@sy...>]

I had to chuckle. I found a guy who did what he considered a text on 
advanced bash programming. (It's not bad but not the direction I'd go.) 
Anyways, it had a line in there about the history facility in bash:

  "Unfortunately, the Bash history tools find no use in scripting."

Enjoy. You'll only see it in action currently in the config menus. I'll 
add it to more user prompts as I go through it.

One more thing. The config parameter BBROOTDIR is now gone. There's no 
need for it since it's hardwired in at install-time.

And for all you people who need a smile, we're picking up our new puppy 
tomorrow morning.

Here's clip of the puppies in the litter

http://www.chowchows.com/video/pups_2008.html

And the proud parents

http://www.chowchows.com/combine.php?sire=23&dam=33

-- 
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

Re: [Bashburn-info] Need some merge help

[Steven W. O. <st...@sy...>]

On Thursday, Sep 18th 2008 at 16:39 -0000, quoth Anders Lind?n:

=>Ok, I merged what was changed in the release branch into trunk (I hope
=>it worked, scream if it didn't).
=>
=>This is how I did it:
=>
=>* Checked out wat which point release/3.0 was created with the log
=>command. Turns out it was at revision 532.
=>
=>* cd into trunk and run the command: 
=>
=>svn merge -r 532:HEAD
=>https://svn.inf.sgsp.edu.pl/svn/bashburn/releases/3.0
=>
=>
=>So, hopefully it all worked out and any changes that took place in 3.0
=>is now merged into trunk. 

Anders, Thank you. Now I understand what my misteak was. I went for 531 
instead of 532. Now the error message makes sense too.

:-)

=>
=>
=>m?n 2008-09-15 klockan 21:47 -0400 skrev Steven W. Orr:
=>> In my own workspace, I
=>> 
=>> cd trunk
=>> I see that the release/3.0 branch was created on rev 531.
=>> I see that we're currently at 544.
=>> 
=>> 708 > svn merge -r 531:544 
=>> https://svn.inf.sgsp.edu.pl/svn/bashburn/release/3.0
=>> svn: REPORT request failed on '/svn/!svn/bc/544/bashburn/release/3.0'
=>> svn: '/svn/!svn/bc/544/bashburn/release/3.0' path not found
=>> 
=>> I also tried
=>> 
=>> 706 > svn merge -r 531:544 ../releases/3.0
=>> svn: Unable to find repository location for '../releases/3.0' in revision 531
=>> 
=>> Does anyone have a hint?
=>> 


-- 
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/

Re: [Bashburn-info] Need some merge help

[Anders L. <and...@gm...>]

Ok, I merged what was changed in the release branch into trunk (I hope
it worked, scream if it didn't).

This is how I did it:

* Checked out wat which point release/3.0 was created with the log
command. Turns out it was at revision 532.

* cd into trunk and run the command: 

svn merge -r 532:HEAD
https://svn.inf.sgsp.edu.pl/svn/bashburn/releases/3.0


So, hopefully it all worked out and any changes that took place in 3.0
is now merged into trunk. 


mån 2008-09-15 klockan 21:47 -0400 skrev Steven W. Orr:
> In my own workspace, I
> 
> cd trunk
> I see that the release/3.0 branch was created on rev 531.
> I see that we're currently at 544.
> 
> 708 > svn merge -r 531:544 
> https://svn.inf.sgsp.edu.pl/svn/bashburn/release/3.0
> svn: REPORT request failed on '/svn/!svn/bc/544/bashburn/release/3.0'
> svn: '/svn/!svn/bc/544/bashburn/release/3.0' path not found
> 
> I also tried
> 
> 706 > svn merge -r 531:544 ../releases/3.0
> svn: Unable to find repository location for '../releases/3.0' in revision 531
> 
> Does anyone have a hint?
> 
-- 
Anders Lindén
http://bashburn.sf.net

Re: [Bashburn-info] A historical idea to throw out :-)

[Anders L. <and...@gm...>]

ons 2008-09-17 klockan 14:32 -0400 skrev Steven W. Orr:
> There are some places in bb where we throw a prompt and ask the user for 
> input, where there are a set of choices that would make sense for the user 
> to type in. I'm not talking about completion. Here's an example (and 
> there are many others):
> 
> +--------------+
> | BashBurn 3.0 |
> +--------------+
> |
> +--------------+ INFORMATION +--------------+
> This option sets the language BashBurn's interface will be shown in.
> The current setting is: English, and below is a list
> of possible languages to choose from.
> To cancel, just press [ENTER].
> +--------------+ INFORMATION +--------------+
> 
> Czech  English  German  Italian  Norwegian  Polish  Spanish  Swedish
> 
> +--------------+-------------+--------------+
> 
> Your Choice? |>
> 
> Wouldn't it be nice for the user to be able to hit ^P or UpArrow and be 
> able to cycle through the only choices that are available?
> 
> I just found out how to do it. (Highly abbreviated example code.)
> 
> ls > tmpfile
> history -c
> history -r tmpfile
> read -r -p 'Your choice? |> '
> 
> Does anyone hate this?
> 

Sound good to me. Simpler and no chance of misspellings. Go for it.

-- 
Anders Lindén
http://bashburn.sf.net

Re: [Bashburn-info] A historical idea to throw out :-)

[Steven W. O. <st...@sy...>]

On Wednesday, Sep 17th 2008 at 14:56 -0000, quoth Markus Kollmar:

=>Steven W. Orr schrieb:
=>> There are some places in bb where we throw a prompt and ask the user for 
=>> input, where there are a set of choices that would make sense for the user 
=>> to type in. I'm not talking about completion. Here's an example (and 
=>> there are many others):
=>>
=>> +--------------+
=>> | BashBurn 3.0 |
=>> +--------------+
=>> |
=>> +--------------+ INFORMATION +--------------+
=>> This option sets the language BashBurn's interface will be shown in.
=>> The current setting is: English, and below is a list
=>> of possible languages to choose from.
=>> To cancel, just press [ENTER].
=>> +--------------+ INFORMATION +--------------+
=>>
=>> Czech  English  German  Italian  Norwegian  Polish  Spanish  Swedish
=>>
=>> +--------------+-------------+--------------+
=>>
=>> Your Choice? |>
=>>
=>> Wouldn't it be nice for the user to be able to hit ^P or UpArrow and be 
=>> able to cycle through the only choices that are available?
=>>
=>> I just found out how to do it. (Highly abbreviated example code.)
=>>
=>> ls > tmpfile
=>> history -c
=>> history -r tmpfile
=>> read -r -p 'Your choice? |> '
=>>
=>> Does anyone hate this?
=>>
=>>   
=>Oh, I think this i a great advantage! Steven your are great! :-)
=>
=>Maybe we should then backup the prior contents of the history file, so 
=>that after exiting bashburn the user has the history as it was before 
=>starting bashburn.

Interesting suggestion. The problem is that it's sort of like a cummerbund 
or a vest. You only get to choose one. ;-)

What we can do is to create a ~/.bashburn_history which would contain all 
of the history items that get gen'd *except* for the entries that would 
happen on input that expected some sort of possible enumeration.

-- 
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/

Re: [Bashburn-info] A historical idea to throw out :-)

[Markus K. <mar...@on...>]

Steven W. Orr schrieb:
> There are some places in bb where we throw a prompt and ask the user for 
> input, where there are a set of choices that would make sense for the user 
> to type in. I'm not talking about completion. Here's an example (and 
> there are many others):
>
> +--------------+
> | BashBurn 3.0 |
> +--------------+
> |
> +--------------+ INFORMATION +--------------+
> This option sets the language BashBurn's interface will be shown in.
> The current setting is: English, and below is a list
> of possible languages to choose from.
> To cancel, just press [ENTER].
> +--------------+ INFORMATION +--------------+
>
> Czech  English  German  Italian  Norwegian  Polish  Spanish  Swedish
>
> +--------------+-------------+--------------+
>
> Your Choice? |>
>
> Wouldn't it be nice for the user to be able to hit ^P or UpArrow and be 
> able to cycle through the only choices that are available?
>
> I just found out how to do it. (Highly abbreviated example code.)
>
> ls > tmpfile
> history -c
> history -r tmpfile
> read -r -p 'Your choice? |> '
>
> Does anyone hate this?
>
>   
Oh, I think this i a great advantage! Steven your are great! :-)

Maybe we should then backup the prior contents of the history file, so 
that after exiting bashburn the user has the history as it was before 
starting bashburn.


Markus

[Bashburn-info] A historical idea to throw out :-)

[Steven W. O. <st...@sy...>]

There are some places in bb where we throw a prompt and ask the user for 
input, where there are a set of choices that would make sense for the user 
to type in. I'm not talking about completion. Here's an example (and 
there are many others):

+--------------+
| BashBurn 3.0 |
+--------------+
|
+--------------+ INFORMATION +--------------+
This option sets the language BashBurn's interface will be shown in.
The current setting is: English, and below is a list
of possible languages to choose from.
To cancel, just press [ENTER].
+--------------+ INFORMATION +--------------+

Czech  English  German  Italian  Norwegian  Polish  Spanish  Swedish

+--------------+-------------+--------------+

Your Choice? |>

Wouldn't it be nice for the user to be able to hit ^P or UpArrow and be 
able to cycle through the only choices that are available?

I just found out how to do it. (Highly abbreviated example code.)

ls > tmpfile
history -c
history -r tmpfile
read -r -p 'Your choice? |> '

Does anyone hate this?

-- 
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

Re: [Bashburn-info] Need some merge help

[Steven W. O. <st...@sy...>]

On Tuesday, Sep 16th 2008 at 09:15 -0000, quoth Anders Lind?n:

=>What are you trying to merge? 
=>We don't want to merge unstable changes into the release branch.

No, the other way. I want to merge the changes in release/3.0 to trunk. I 
made changes in 3.0 which for better or for worse are now working and I 
wanted to get them into trunk before I continue working there.




=>
=>
=>m?n 2008-09-15 klockan 21:47 -0400 skrev Steven W. Orr:
=>> In my own workspace, I
=>> 
=>> cd trunk
=>> I see that the release/3.0 branch was created on rev 531.
=>> I see that we're currently at 544.
=>> 
=>> 708 > svn merge -r 531:544 
=>> https://svn.inf.sgsp.edu.pl/svn/bashburn/release/3.0
=>> svn: REPORT request failed on '/svn/!svn/bc/544/bashburn/release/3.0'
=>> svn: '/svn/!svn/bc/544/bashburn/release/3.0' path not found
=>> 
=>> I also tried
=>> 
=>> 706 > svn merge -r 531:544 ../releases/3.0
=>> svn: Unable to find repository location for '../releases/3.0' in revision 531
=>> 
=>> Does anyone have a hint?
=>> 
=>-- 
=>Anders Lind?n
=>http://bashburn.sf.net
=>

-- 
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/

Re: [Bashburn-info] Need some merge help

[Nick W. <ni...@uk...>]

On Mon, 15 Sep 2008 21:47:58 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> In my own workspace, I
> 
> cd trunk
> I see that the release/3.0 branch was created on rev 531.
> I see that we're currently at 544.
> 
> 708 > svn merge -r 531:544 
> https://svn.inf.sgsp.edu.pl/svn/bashburn/release/3.0
> svn: REPORT request failed on '/svn/!svn/bc/544/bashburn/release/3.0'
> svn: '/svn/!svn/bc/544/bashburn/release/3.0' path not found
> 
> I also tried
> 
> 706 > svn merge -r 531:544 ../releases/3.0
> svn: Unable to find repository location for '../releases/3.0' in
> revision 531
> 
> Does anyone have a hint?
> 

Ummm. No :-D

I have never done that either.  I am nearly finished decorating, so
soon will have more time to get up to speed with all this.

BTW, if you use KDE, there is an excellent app called 'kdesvn' - I used
to use it a lot when I was on KDE, but the last year or so now I use
Fluxbox.

http://kdesvn.alwins-world.de/

Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] Need some merge help

[Steven W. O. <st...@sy...>]

In my own workspace, I

cd trunk
I see that the release/3.0 branch was created on rev 531.
I see that we're currently at 544.

708 > svn merge -r 531:544 
https://svn.inf.sgsp.edu.pl/svn/bashburn/release/3.0
svn: REPORT request failed on '/svn/!svn/bc/544/bashburn/release/3.0'
svn: '/svn/!svn/bc/544/bashburn/release/3.0' path not found

I also tried

706 > svn merge -r 531:544 ../releases/3.0
svn: Unable to find repository location for '../releases/3.0' in revision 531

Does anyone have a hint?

-- 
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

[Bashburn-info] YAFTI

[Steven W. O. <st...@sy...>]

Yet Another Fix to Install.sh.

When the symlink is created, Install will make sure that the bin directory 
exists, by creating it if necessary.

All cp and mkdir commands will now cause an abort if they fail.

The prefix variable will now have a trailing / removed if it's there.

(I guess I'm seeing why we want this to have been in trunk. Sorry.)

-- 
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

Re: [Bashburn-info] I changed the Install.sh script.

[Steven W. O. <st...@sy...>]

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/

Re: [Bashburn-info] I changed the Install.sh script.

[Nick W. <ni...@uk...>]

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

Re: [Bashburn-info] I changed the Install.sh script.

[Nick W. <ni...@uk...>]

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

Re: [Bashburn-info] I changed the Install.sh script.

[Nick W. <ni...@uk...>]

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

Re: [Bashburn-info] I changed the Install.sh script.

[Steven W. O. <st...@sy...>]

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/

Re: [Bashburn-info] I changed the Install.sh script.

[Steven W. O. <st...@sy...>]

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/

Re: [Bashburn-info] I changed the Install.sh script.

[Nick W. <ni...@uk...>]

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

Re: [Bashburn-info] I changed the Install.sh script.

[Nick W. <ni...@uk...>]

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

Re: [Bashburn-info] I changed the Install.sh script.

[Nick W. <ni...@uk...>]

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

Re: [Bashburn-info] I changed the Install.sh script.

[Steven W. O. <st...@sy...>]

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/

[Bashburn-info] I changed the Install.sh script.

[Steven W. O. <st...@sy...>]

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

Re: [Bashburn-info] All tabs are now removed from configure and advanced.lang's

[Steven W. O. <st...@sy...>]

On Friday, Sep 12th 2008 at 23:27 -0000, quoth Markus Kollmar:

=>Steven W. Orr wrote:
=>> Markus, I hope this is ok.
=>>
=>>   
=>--> Steven, it is ok and great idea, that you now have removed all 
=>cosmetic tabs from all language files.
=>
=>--> I have added "bb_main_menu=MAIN" to file "BashBurn.lang" in all 
=>language files like you want it, or Steven?
=>An exception is the SWEDISH translation:
=>Anders (or Steven), what coding system did you use in your editor to 
=>encode/decode this files? My emacs gave me a message while I wanted to 
=>save the swedish file, that the correct encoding system has to select in 
=>order to save the file savely. Did you use utf8? Maybe we should make 
=>also guidlines which coding system to use?
=>
=>--> Steven please note (info manual of "gettext (libintl library, 
=>version 0.16.1)"):
=>"GNU `bash' 2.0 or newer has a special shorthand for translating a
=>string and substituting variable values in it: `$"msgid"'.  But the use
=>of this construct is *discouraged*, due to the security holes it opens
=>and due to its portability problems."
=>
=>To localize a sentence like
=>  echo -e "Hello\tworld!"
=>we can use
=> echo -e "`gettext \"Hello\\tworld\"`"
=>
=>--> By the way I still have the problem that I got no german translation 
=>in the sub-menues of configuration. Is this only local problem to me?
=>
=>
=>(Oh... time to go to bed... ;-)  )
=>
=>Markus

I'll do some more reading on the proper use of $"stuff". It may be that we 
should stick to the lang files, but localize the usage of gettext to those 
files.

bb.en.lang:

bbhellothere=$"Hello there"

Then 

  echo -e $(gettext "$bbhellothere")


This way, the --dump-po-strings will work *for* us and by convention, we 
would only use $"stuff" in places where nothing dangeous could be eval'd.

I'll be gone tomorrow. We're driving to New York. We're buying a new 
Chowchow. :-)

http://www.chowchows.com/

-- 
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