Re: Horde components, deprecating old pear compontent

On Thu, Nov 10, 2011 at 11:59 PM, Daniel O'Connor <daniel.oconnor@gmail.com>wrote: > > > > > >> The biggest hurdle is the PEAR installer has no support for a package > >> migrating channels - if the code vanishes from the PEAR channel; it > breaks > >> people's systems. I've been meaning to take a look at how hard it could > >> be; > >> but have never had the time really. > >> > >> We have deleted some content from SVN or from PEAR, but only when it's > had > >> ridiculously low downloads over 6 years or so and isn't installable at > >> all. > >> > > > > I'm wondering if we can leverage the info in pearweb. E.g. it already > > notes that a package is superceeded or deprecated in favour of another > > package. Isn't that pretty much the same? I mean, the channel (aka > > location) shouldn't matter. > > > > I really don't know enough about the inner workings of the installer and > the pear channel backend stuff. Maybe it's as simple as a HTTP redirect on > the backend, maybe it's more complicated. > > I should get forking from https://github.com/pear/pear-core and > look at > what can be done. > Did pear-core move 'officially' to github? Just wondering where the best way to commit is?