RE: [PEAR-DEV] [RFC] CVS directory structure
| From: | Lukas Smith | Date: | Sat, 15 Nov 2003 15:41:16 +0000 |
| Subject: | RE: [PEAR-DEV] [RFC] CVS directory structure | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23644@lists.php.net to get a copy of this message | ||
> From: Chuck Hagenbuch [mailto:chuck@horde.org]
> Sent: Saturday, November 15, 2003 4:34 PM
> What if your package is Image_Text_Diagonal? (Don't get picky about the
> example
> and whether or not it should be part of Image_Text, the point is that you
> have
> a 3-level deep package). By your scheme, you'd be adding two directories
> to
> that structure before you get to the files, right? Image/Text/ then you
> have
> stuff.
>
> So your proposal adds one directory for every level of depth of the
> package over
> 1. Not just 1 always.
Correct.
> Btw, is it *really* that hard to keep a package.xml file up to date? If
> you want
> the right to have an utterly broken package.xml file, which is the
> argument
> that I heard in a few places in this thread, then you probably *should* be
> developing outside of PEAR CVS. There's no reason that even an alpha-level
> package shouldn't have a valid package.xml that makes it installable.
Why would you want to install something that is so heavy under development
that it is not being released? Why is everybody so keen to add extra steps
that add no value what so ever. In my opinion they are not only annoying but
simply add the chances for inconsistencies (like forgetting to copy a file)
and confusion (like forgetting to move down to an actually released version
of the package).
Regards,
Lukas