harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hindess (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-4911) Proposed improvements to create_links.sh for snapshot builds
Date Tue, 09 Oct 2007 10:32:51 GMT

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

Mark Hindess updated HARMONY-4911:
----------------------------------

    Attachment: create_links.sh

> Proposed improvements to create_links.sh for snapshot builds
> ------------------------------------------------------------
>
>                 Key: HARMONY-4911
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4911
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Website/Documentation
>            Reporter: Mark Hindess
>            Assignee: Stepan Mishura
>            Priority: Minor
>         Attachments: create_links.sh
>
>
> Stepan,
> I think there are a few issues with the current implementation of the "permanent" links
to the latest snapshots:
> 1) When a user downloads the file the name still contains 'latest' and not the revision
number.  This means it isn't so obvious which version of the file it really is.  (Fixing this
doesn't break processes because processes using wget/snarf/etc can specify a specific output
name if that is required.)  I suggest we have create_links.sh build a .htaccess file of redirects
rather than using symlinks.
> 2) The names remove the work apache and replace it with latest.  This seems a little
inappropriate to me.
> 3) The mapping between filenames and latest links is complicated.  I think long term
it would be simpler to have a one-to-one mapping (essentially replace 'r[0-9]*' with 'latest')
then create_links.sh can be made smart enough not require three (four with .asc files) lines
to be added each time we add a new platform.
> 4) The snapshots download directory contains a README.html file.  This gets rendered
at the bottom of the page.  I suggest using HEADER.html which gets
> rendered at the top.  If we get create_links.sh to create the HEADER.html then it can
list the permanent links in a more concise format.
> 5) The create_links.sh script is visible in the directory index.  I suggest having create_links.sh
add an 'IndexIgnore' directive to the .htaccess file it creates so that it doesn't clutter
up the listing - ditto for any other non-user files.
> I'll attach an alternative version of the create_links.sh script to this JIRA.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message