Re: PECL versioning

On Wed, Mar 19, 2008 at 11:23 PM, Steph Fox <steph@zend.com> wrote: > > I did not see any announce on internal about that :) About IRC, well, > > that's no place to announce anything :-) > > Over 40 emails on the subject, at the end of January. Blink and you'd have > missed it. First, if you are talking about the random discussions in completely unrelated topic, yes. I remember some comments about pecl. If you are talking about an actual discussion about PECL on internals (why not on pecl-dev), then no, I can't find any. > >> > There is only one safe way, the package version. The other > >> > informations (either in the various headers or the rc) are rarely > >> > updated or even used. > >> > >> That's... not safe either. It's where I'd pick up info for releases, > >> sure, > >> but it's not safe info for pecl4win/snaps. > > > > I made many tests and ask a couple of extensions developer, the best > > way could be to let them define what to use where. It can work for the > > snapshots, the releases or custom builds done on demand. We only need > > to add the necessary info in peclweb (DB, forms, cvs interface to list > > the branches for a given ext, etc.). The build system can work easily > > by creating a tree from various sources. That's what did the person I > > was refering to in the beggining of this mail. It is really flexible > > and should allow us to provide whatever we need. > > We're obviously not having the same conversation. Giving up on this exchange > :) You are confusing. But if you don't want to discuss, that's your choice. Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org