These are valid points, and would be considered within the design of an upgrade tool.
But a better scenario would be that the package developer/designer would consider upgrades. The big issue being add/change/deleted variables, and/or new or deleted features. If the package developer considered upgrades, they could use a previous version's config file(s), and when encountered, make the necessary modifications to it (based upon the new version's variable and feature changes) to do the upgrades. That would seem the easier situation, but I resigned myself to the fact that that wasn't going to happen, so thought maybe another approach would have to do. As someone else suggested, the WebConf tool doesn't help in an upgrade scenario. It's a great tool, but it isn't of great assistance to the upgrade process - it helps for maintenance tasks and monitoring (I use it all the time). For those that work on this product, please don't misinterpret what I saying. I like LEAF Bering uClibc. I wouldn't be using it if I didn't. I've only brought this up because this has been the painful part of using Bering uClibc. I set up multiple LEAF Bering uClibc systems (for friends, and small organizations), and upgrading them becomes very cumbersome and painful. This discussion seems to be moot because it doesn't seem like too many people are interested anyway. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of groups, freeman Sent: Sunday, December 04, 2005 10:38 PM To: [email protected] Subject: Re: [leaf-user] RE: Bering uClibc Package Updates I'm of the mindset that this is, for all practical intents and purposes, ill advised and here's my reasoning. The packages are the products of various authors, Tom Eastep for one. Unless he and all contributors were to adhere to some protocol there's the definite potential for problems. Consider that (for example) the shorewall config files often contain documentation within them. If one uses an older config file in its entirety then one will lose the documentation of new features that was within the newer config file. The old config might well work fine and as expected, but you'd not be aware of new features because the docs were in the newer config files. And there's of course the possibility of non-backward-compatibility (maybe not outright bustage but unexpected/unforeseen effects). Also, seeking support for a newer installation with older config files might leave the supporting folks confused. I have no complaint with what Tom (et al) does - I can't even fathom how things /could/ be done differently, let alone the imposition of 'compatibility protocols' upon such participants for whose work and contributions I am so grateful. I'd definitely love to see something like this but have resigned myself to death, taxes, gravity and tedious LEAF upgrades. FWIW I'm still using LEAF (BuC 2.3), 'bout 5 years after discovering this project. A thank you to Brad for seeing a 'problem' and expressing willingness to attempt to tackle it though! scott; canada (a wistful sigh, thinking back to Eigerstein days :) [EMAIL PROTECTED] wrote: >I have wondered if there was any better method for upgrading from a previous version of Bering uClibc, and I assumed that what Charles said below was the best possible solution. > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
