incubator-zeta-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Fahlke <flyingm...@googlemail.com>
Subject Re: Migrating Zeta Componetns to Github
Date Fri, 20 Apr 2012 12:39:17 GMT
Am 20. April 2012 14:35 schrieb James Pic <jamespic@gmail.com>:

> On Fri, Apr 20, 2012 at 2:26 PM, Derick Rethans <derick@apache.org> wrote:
>
> > On Fri, 20 Apr 2012, James Pic wrote:
> >
> > > Can't apache just pass the repo to say Derick or something ?
> > >
> > > https://github.com/apache/zetacomponents
> >
> > I think we should split it up, so that we can/could orphan specific
> > components. I doubt anybody wants to maintain "PhpGenerator" f.e.
> >
>
> I love this idea ! Make zeta components a coding standard rather than a
> centralized repo of libraries is kind of the holy grail for me ...
>
> In that case I only see one issue: dependency management. How should the
> user specify that he wants this and that component of this or that version
> ?
>
> What if a user wants to depend on a component in its trunk version, or even
> from his personal fork ? It should be super easy if we want people to fork
> and issue pull requests.
>
> I am not aware that PEAR is capable of installing stuff directly from
> github, like pip does for python*. I eared compozer would be able to do
> that one day.
>
> I think it's worth the experiment.
>
> Regards
>
> *
>
> http://blog.yourlabs.org/post/19725807220/django-pinax-virtualenv-setuptools-pip
>


Have a look at http://getcomposer.org/
it makes this custom cases a lot easier (but it breaks sometimes, as it is
still in development and has severel commits per day)

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message