Re: Amsterdam meeting agenda
| From: | Jon Parise | Date: | Sat, 10 Apr 2004 09:48:40 +0000 |
| Subject: | Re: Amsterdam meeting agenda | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-27380@lists.php.net to get a copy of this message | ||
On Sat, Apr 10, 2004 at 11:40:31AM +0200, Bertrand Mansion wrote:
> >> - Where to find the source, online ?
> >> ------------------------------------------------------------
> >> I hate it when the package I am interested in doesn't have its source in
> >> PEAR CVS. I have to download it, untar it, read the source in an IDE. I
> >> suggest that every packages should be available for browsing in CVS or
> >> Subversion repositories with online access. Or at least as .phps.
> >
> > Feel free to discuss this, but I don't think it's practical to require
> > all PEAR source code to exist in a public repository. While it may be
> > inconvenient for you to browse the source code because you need to
> > download a distribution archive, it may be even more inconvenient for
> > the package's developers to maintain their code in a public repository.
> > I think the developers' preference should always take precedence here.
>
> That's why I said .phps too.
Sorry, I missed that. I think that's a reasonable request.
> It is nice to have the choice. Still, IMO we shouldn't have to
> download the package in order to just browse the sources.
I agree. It's important that the developers retain the right to
choose the method that works best for them.
> That's maybe something that could be done in PEAR web too, convert
> the release .tar.gz to browsable code. Or maybe that's just a
> gadget?
I think that's a very good idea. There was talk of running
phpDocumentor on all released code and making the result available on
the PEAR web site. A side effect of that would be the generation of
browsable source code, as well.
--
Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)