Re: Importing packages into CVS

Chuck Hagenbuch wrote: > Quoting Christian Weiske <cweiske@cweiske.de>: > >> After it seems that most people agreed that having all packages in our >> CVS, I would like to do the work and import every version of every >> package currently not in PEAR CVS into CVS. > > If this is done I am sorry to say that the PEAR versions of the > following packages will be forks and will not be maintained by their > current leads: > > File_PDF > Net_SMS > Text_Diff > VFS > XML_SVG > > The first four will be maintained and available as part of Horde and > from Horde's pear channel. XML_SVG will likely be dropped entirely due > to lack of use. Hi Chuck, Are you suggesting that these packages will be withdrawn from PEAR simply because we wish to keep a copy of the code in cvs.php.net? The packages already have bug trackers at pear.php.net, and all releases through pear.php.net as well as in Horde, there's no reason to do anything drastic. Please do not misinterpret this to be a wresting of code control away from the maintainer! It is an effort to provide redundancy and a fail-safe in the event that a package maintainer disappears. For active packages such as the ones you've listed, it may make sense to provide some kind of automated system for synchronizing the repositories, so that cvs.php.net is up-to-date with changes to the primary repository. Perhaps, since Christian proposed the change, he would be willing to set up a synchronization cron job on one of his servers? Greg