Re: Config class running

<chregu@bitflux.ch> wrote : > Hi > > I have no problem with a rewrite and commiting that to CVS, but as it > looks like you're changing the API of a stable class signficantly: How > do we warn the people about that, and how can I download the old class > later, when the new API is released. Or is this not possible anymore then > and I have to rewrite my scripts, if i want to redestribute them. I know, > that I can redistribute the old Config classes to avoid this stuff, but > anyway... > > These are just some questions, which popped up in my head. I'm not against > introducing a rewrite, but could you maybe release it somewhere, so > we can have a look at it :) Hi Christian, I've setup a page where you can see the source: http://www.mamasam.com/Config/index.html There might be a way to keep the last Config class for as long as you want to maintain it by using the pear installer. I could call my class Config 2.0 while yours will still be 1.x ? With the pear installer, users can choose which version of a package they want to install. In the CVS, it might also be possible to create a new branch if you want to continue to work on your config class. Unfortunately, I am not really CVS aware, so other developers might confirm... :) Tell me what you think of the new class and if you see a way to make the transition easier for you. Cheers, Bertrand Mansion Mamasam