Re: why bloated packages are bad (a case for splitting up large packages)

On Sun, 2005-08-14 at 21:09 -0700, Ian Eure wrote: > On Sunday 14 August 2005 08:43 pm, Greg Beaver wrote: > > Hello, > > > > There has been a lot of wrangling over PEAR_ErrorStack splitting off > > from PEAR recently. It is important to understand why this is a good > > idea. PEAR_ErrorStack is a single file. Developers wishing to use > > PEAR_ErrorStack at present have implicit dependencies on Archive_Tar and > > Console_Getopt because PEAR requires them, even though they have nothing > > to do with PEAR_ErrorStack. > > > On this subject, do you care to answer Joe's question regarding the correct > process for splitting a monolithic package up into subpackages? Do the > individual subpackages have to go through PEPr, or can someone be contacted > to set them up? No they don't, just register them as new package but email pear-dev or such before hand to make note of this, to get some discussion going on why and if it's needed (which it is in the payment case) And thus the pear admins will accept and voila it's all done :-) No need to move things around in CVS or anything, just create a new package xml file for each new sub package, look at the Validate CVS or MDB2 to see how we handle package files for sub packages. - Helgi