Re: why bloated packages are bad (a case for splitting up large packages)
| From: | Ian Eure | Date: | Mon, 15 Aug 2005 04:09:49 +0000 |
| Subject: | Re: why bloated packages are bad (a case for splitting up large packages) | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-39359@lists.php.net to get a copy of this message | ||
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?
> The MIME_Type [package] is used to differentiate
> between unknown file extensions I believe (a very good thing), but this
> will not be used by all users of File_Archive.
>
I actually split this functionality out of MIME_Type and into a patch for
PHP_Compat[1], though it hasn't made it in yet. Simply calling
mime_content_type() should be the correct thing to do in this case once that
gets in, so that part of the problem will be alleviated.
[1]: http://pear.php.net/bugs/4691
Attachment: [application/pgp-signature]
Attachment: [application/pgp-signature]