You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Chris Lambertus (JIRA)" <ji...@apache.org> on 2016/05/02 23:07:12 UTC

[jira] [Updated] (INFRA-11702) Dist folder layout change for Apache Commons - use symlinks?

     [ https://issues.apache.org/jira/browse/INFRA-11702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Lambertus updated INFRA-11702:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

Is this waiting on Infra for anything?

> 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 disk)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)