Re: [Bashburn-info] Substantial change to the configure function.
Brought to you by:
bashburn
|
From: Steven W. O. <st...@sy...> - 2008-09-03 14:49:11
|
On Wednesday, Sep 3rd 2008 at 10:39 -0000, quoth Nick Warne:
=>On Wed, 3 Sep 2008 10:30:34 -0400 (EDT)
=>"Steven W. Orr" <st...@sy...> wrote:
=>
=>> On Wednesday, Sep 3rd 2008 at 10:13 -0000, quoth Nick Warne:
=>>
=>>
=>> =>Still doesn't save any changes to configuration. It shows the
=>> changed =>value* perfectly (good idea!), but applying changes doesn't
=>> save.
=>>
=>> I deleted all src files, deleted $BBROOT and re-updated. I also found
=>> a small change that got lost that has nothing to do with this.
=>>
=>> We're currently at 496 and it seems to work fine. Can you make sure
=>> you're in sync?
=>>
=>
=>Yep, current version.
=>
=>I just deleted .bashburnrc and uninstalled/re-installed. Same issue.
=>
=>I can change something, and see it marked*. The 'apply changes'
=>doesn't change it - as the value reverts back to the old value.
=>
=>As an aside, in Bashburn.sh there is duplicate sourcing of
=>
=>. ${BBROOTDIR}/misc/commonfunctions.sh
I fixed the dup. I have no idea what else to say. Can you diff this
attachment with what you have?
--
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 |