Re: quick question about pearweb and package.xml 2.0

[CC'ing pear-webmaster] On Wed Sep 22, 2004 at 06:2436PM -0400, Greg Beaver wrote: > Martin Jansen wrote: > >>Basically, dependencies could be tracked in a new table, "deps2" > > > > > >Do you see a chance to convert the old dependency table to the new > >format? > > Actually, this would be really easy to do, since the whole point was the > new format represents every possible set of the old format, plus some > other cases it couldn't represent (such as allowing versions 1.3-1.4, no > 1.5 and 1.6-2.0) Good. > >FYI, in the current version dependency are not registered per release, > >but per package only. Actually this doesn't make much sense, but such > >is life ;-). > > That is an interesting problem, It seems the best thing to do would be > to go safe, and implement the new table as deps2. Once it is verified > to be working, we can delete the old deps table and replace with the new > deps2 as deps. > > We definitely need per-release deps information, just in case an > application has a recommended dep on an older version. Sure. > How difficult do you think it might be to set up a php5 server that is > independent of pear.php.net for a separate php5-only channel? Technically this isn't really that hard: I'd suggest to set up another Apache instance on sth. like http://pear.php.net:81/. Or we are going to switch the whole website to PHP 5. > If it > isn't too tough, then setting up PEAR_Server for this with an > independent database would be a cinch. Would this require people to subscribe to a special channel to get PHP 5-only packages? -- - Martin Martin Jansen http://martinjansen.com/