Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Sun, 2008-11-30 at 14:50 +0100, Tobias Scherbaum wrote:
> Jan Kundrát:
> > Diego 'Flameeyes' Pettenò wrote:
> > > I have a very quick proposal: why don't we move the packages' homepage
> > > in metadata.xml (since it's usually unique for all the versions)
> >
> > I believe the reason was that HOMEPAGE might change with new versions
> > and that metadata.xml didn't (doesn't?) support version-specific data.
>
> In most (nearly all?) cases a HOMEPAGE change does also affect older versions.
> Does someone have an example where older versions stay at an old homepage
> and newer versions moved to a new homepage? Which (and how many) packages would be affected by that?
I've seen this happen for at least one ruby package where the package
got forked, with the old stagnant versions still on the old homepage and
the new versions on the new homepage.
I still favor the move to metadata.xml, even though there are probably a
few more edge cases like this.
Kind regards,
Hans
|
| Attachment: |
|
signature.asc (This is a digitally signed message part)
|
|
