RE: [SVN-MIGRATION] Re: Proposed repository structure
| From: | Andi Gutmans | Date: | Tue, 02 Sep 2008 20:59:09 +0000 |
| Subject: | RE: [SVN-MIGRATION] Re: Proposed repository structure | ||
| References: | 1 2 3 4 5 6 | Groups: | svn.migration |
| Request: | Send a blank email to svn-migration+get-75@lists.php.net to get a copy of this message | ||
I think renaming to php/ is a good idea.
Re: Zend & TSRM I agree that it'll be more convenient to have them within php/. It's
been a PITA to manage them separately. However, we should still continue to have the architecture
componentized (incl. other pieces like SAPI) and it should therefore not affect the build itself
(except for naming/path changes).
Andi
> -----Original Message-----
> From: Wez Furlong [mailto:wez.furlong@messagesystems.com]
> Sent: Tuesday, September 02, 2008 1:21 PM
> To: Johannes Schlüter
> Cc: Gwynne Raskind; svn-migration@lists.php.net
> Subject: Re: [SVN-MIGRATION] Re: Proposed repository structure
>
> Seeing as php-src is a hangover from CVS modules headaches, can we
> rename that to just "php"?
>
> php/
> trunk/
> Zend
> TSRM
> ext
>
> --Wez.
>
> On Sep 2, 2008, at 4:17 PM, Johannes Schlüter wrote:
>
> > On Tue, 2008-09-02 at 15:46 -0400, Gwynne Raskind wrote:
> >> php-src/
> >> trunk/
> >> zend/
> >> tsrm/
> >> ext/
> >
> > We definitely keep the spelling there, aka. "TSRM" and "Zend" else we
> > can change basically *all* files in the source.
> >
> >> Yes, this gives every single PEAR and PECL extension its own
> >> branches,
> >> tags, and trunk; I feel this necessary.
> >
> > See other mail for discussion about that ;-)
> >
> > johannes
>
>
> --
> SVN Migration Project Mailing List (http://svn.php.net)
> To unsubscribe, visit: http://www.php.net/unsub.php