Re: [SVN-MIGRATION] Reorganization and splitting
| From: | Andrei Zmievski | Date: | Thu, 30 Oct 2008 17:46:55 +0000 |
| Subject: | Re: [SVN-MIGRATION] Reorganization and splitting | ||
| References: | 1 2 3 4 5 6 7 | Groups: | svn.migration |
| Request: | Send a blank email to svn-migration+get-119@lists.php.net to get a copy of this message | ||
For the record, I talked to Gwynne on IRC and said GTK would need its own repo, but I was under the impression that this was something that was required. If it's not, I'm just fine with keeping it all in the same repo.
-Andrei
Gwynne Raskind wrote:
On Oct 29, 2008, at 9:25 PM, Wez Furlong wrote:It's a maitenance question. Each repository has its own authorization/authentication scheme, set of hook scripts, etc. For people like GTK and PEAR, these would be an improvement over the current merged setup. PECL and php-src will stay together. -- Gwynne, Daughter of the Code "This whole world is an asylum for the incurable."Yeah, there's no problem with being selective about what you checkout. My question was more from a perspective of what do we gain by having separate repos, when we lose for PECL (in particular) the ability to merge (and track) changes between php-src and PECL. FWIW, I'm strongly opposed to having php-src and pecl be in separate repos, because this kind of merging happens often.Want != need... what's the technical reason for having multiple repos?I'm not sure I understand fully same repo vs. multiple repos issue - so if PECL lives in php-src repo, does it mean I can easily check out PHP source without checking out PECL?