www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-11702) Dist folder layout change for Apache Commons - use symlinks?
Date Thu, 28 Apr 2016 12:46:12 GMT

    [ https://issues.apache.org/jira/browse/INFRA-11702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262077#comment-15262077

Sebb commented on INFRA-11702:

We have been having further discussions about this on the Commons Dev list.
I think it only makes sense if all the versions of all the Commons components are available
from the new URLs.
That would mean adding links (soft or hard) to archive.apache.org as well.

Would that be feasible?

> Dist folder layout change for Apache Commons - use symlinks?
> ------------------------------------------------------------
>                 Key: INFRA-11702
>                 URL: https://issues.apache.org/jira/browse/INFRA-11702
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: Dists
>            Reporter: Stian Soiland-Reyes
> Apache Commons are discussing a change of its dist.apache.org folder layout:
> http://mail-archives.apache.org/mod_mbox/commons-dev/201604.mbox/%3CCAOGo0VaTDvAXGj%3D0RmJW2g2-6PHezEke0VC6rK-YF%2BY1fNKuaw%40mail.gmail.com%3E
> If for consistency we want to svn mv also all the existing releases - but don't want
to break every download link (e.g. for components not updated since 2013) - is it OK for us
to do svn symlinks from the old to new (or opposite) layout?  
> Or would the mirrors basically then download and host an additional 500 MB (current size
of https://dist.apache.org/repos/dist/release/commons/ ) - and basically be a bit upset?
> BTW - I don't think we want to change the layout of all the older releases on https://archive.apache.org/dist/commons/
- but moving the existing current releases would naturally cause duplication on archive -
which I assume is OK.
> (we can always do the symlinks from new layout to old layout to prevent duplicates on

This message was sent by Atlassian JIRA

View raw message