<br><br><div class="gmail_quote">2011/8/9 Alex Mandel <span dir="ltr"><<a href="mailto:tech_dev@wildintellect.com">tech_dev@wildintellect.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I have major concerns from a management perspective about not having<br>
version numbers in the files themselves. Especially with how many files<br>
get generated.<br></blockquote><div><br></div><div>Absolutely agree! I'll create a ticket with a proposal how to solve. I know that there are many more variable values coming from build itself, like all the other disk space requirements in GB, usernames and passwords (defined in passwords.txt and redundant in different quickstart guides) as well as menu path for the different applications (to start).</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
We already have an odd issue (though not sure if it's just<br>
horders/spammers) where some of the older versions are still heavily<br>
downloaded. The title makes it obvious to an end user which version they<br>
have in case they come asking for help.<br></blockquote><div><br></div><div>I guess if we have more time ;) after the current release is out, I can take a look into the etension framework for sphinx, maybe we can create some own to solve the requirements (dynamic concatenated url for image:: target: directive ..</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Thanks,<br>
Alex</blockquote><div><br></div><div>Thank you for your feedback</div><div> </div><div><meta charset="utf-8">Frank</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">
On 08/09/2011 04:33 AM, Cameron Shorter wrote:<br>
> Frank,<br>
> As per one of your suggestions, I think that we are too close to 5.0<br>
> release, and as such shouldn't be introducing anything new like this<br>
> proposal. Lets come back and revisit for the next release.<br>
><br>
> On 09/08/11 20:39, Frank Gasdorf wrote:<br>
>> Update on this:<br>
>><br>
>> Replacement within target URLs for images isn't possible yet. I found<br>
>> an other solution but this would lead to images without links in the<br>
>> first step. And here is what I plan to do:<br>
>><br>
>> 1. enable extension "sphinx.ext.extlinks" in conf.py :<br>
>><br>
>> extensions = [ 'sphinx.ext.extlinks' ]<br>
>><br>
>><br>
>> 2. define an extlink for the download area in conf.py :<br>
>><br>
>> base_download_release_url=<br>
>><br>
>> '<a href="http://download.osgeo.org/livedvd/release/%(projectversion)s/%(variable)s" target="_blank">http://download.osgeo.org/livedvd/release/%(projectversion)s/%(variable)s</a><br>
>><br>
>><br>
</div>>> <<a href="http://download.osgeo.org/livedvd/release/%%28projectversion%29s/%%28variable%29s" target="_blank">http://download.osgeo.org/livedvd/release/%%28projectversion%29s/%%28variable%29s</a>>'<br>
<div class="im">>><br>
>> % { 'projectversion': version,'variable':'%s'}<br>
>><br>
>> extlinks = {<br>
>><br>
>> 'osgeolive-download': (base_download_release_url, 'filename ')<br>
>><br>
>> }<br>
>><br>
>><br>
>> 3. usage in download.rst page:<br>
>><br>
>> [..]<br>
>> .. image:: ../images/download_buttons/download-vm.png<br>
>> :align: left<br>
>><br>
>> :osgeolive-download:`osgeo-live-vm.7z: <osgeo-live-vm.7z>`<br>
>> (|osgeo-live-vm-7z-size|)<br>
>> [..]<br>
>><br>
>><br>
>> 4. same procedure for the md5 files :<br>
>><br>
>> :osgeolive-download:`osgeo-live-vm.7z.md5 <osgeo-live-vm.7z.md5>`<br>
>><br>
>><br>
>> I would suggest to rename the files that the version number is not<br>
>> included anymore. The download area has the dynamic version number<br>
>> taken from the VERSION.txt file (for example:<br>
>> <a href="http://download.osgeo.org/livedvd/release/%(projectversion)s/" target="_blank">http://download.osgeo.org/livedvd/release/%(projectversion)s/</a><br>
</div>>> <<a href="http://download.osgeo.org/livedvd/release/%%28projectversion%29s/" target="_blank">http://download.osgeo.org/livedvd/release/%%28projectversion%29s/</a>><br>
<div class="im">>> would lead into <a href="http://download.osgeo.org/livedvd/release/5.0/" target="_blank">http://download.osgeo.org/livedvd/release/5.0/</a> if<br>
>> VERSION.TXT has the line "5.0" in it )<br>
>><br>
>> But in this case its necessary to change ISO naming procedure...<br>
>> Please have a look at the patch file coming along with this mail.<br>
>><br>
>> pros:<br>
>> * single point to define download URL's<br>
>> * translators do not have to care about renaming<br>
>> * no version update required in rst files anymore<br>
>> cons:<br>
>> * update of shell scripts required for naming of ISO and 7z as well<br>
>> as md5 files (I have no chance to try the build with patched shell<br>
>> scripts)<br>
>> * changes would be close to release day, maybe it's better to change<br>
>> after 5.0 release ...<br>
>><br>
>> What do you think? Any opinions?<br>
>><br>
>> Cheers, Frank<br>
>><br>
>><br>
>> 2011/7/7 Alex Mandel <<a href="mailto:tech_dev@wildintellect.com">tech_dev@wildintellect.com</a><br>
</div>>> <mailto:<a href="mailto:tech_dev@wildintellect.com">tech_dev@wildintellect.com</a>>><br>
<div class="im">>><br>
>> On 07/07/2011 11:37 AM, Frank Gasdorf wrote:<br>
>> > 2011/7/7 Alex Mandel <<a href="mailto:tech_dev@wildintellect.com">tech_dev@wildintellect.com</a><br>
</div>>> <mailto:<a href="mailto:tech_dev@wildintellect.com">tech_dev@wildintellect.com</a>>><br>
<div><div></div><div class="h5">>> ><br>
>> >> Frank,<br>
>> >><br>
>> >> No there is not a deployment script which uploads the ISOs,<br>
>> it's much<br>
>> >> more complicated than you think since that url is actually<br>
>> redirected to<br>
>> >> a tool that then sorts people's downloads amongst the 5 mirrors.<br>
>> >><br>
>> >> The url as defined by the last release will be correct for the<br>
>> next<br>
>> >> release.<br>
>> >> Where:<br>
>> >><br>
>> >><br>
>><br>
>> <a href="http://download.osgeo.org/livedvd/release/[version]/osgeo-live-[version].iso" target="_blank">http://download.osgeo.org/livedvd/release/[version]/osgeo-live-[version].iso</a><br>
>><br>
>> >><br>
>> >><br>
>> >><br>
>><br>
>> <a href="http://download.osgeo.org/livedvd/release/[version]/osgeo-live-mini-[version].iso" target="_blank">http://download.osgeo.org/livedvd/release/[version]/osgeo-live-mini-[version].iso</a><br>
>><br>
>> >><br>
>> >><br>
>> >><br>
>><br>
>> <a href="http://download.osgeo.org/livedvd/release/[version]/osgeo-live-vm-[version].7z" target="_blank">http://download.osgeo.org/livedvd/release/[version]/osgeo-live-vm-[version].7z</a><br>
>><br>
>> >><br>
>> >> End up as:<br>
>> >> <a href="http://download.osgeo.org/livedvd/release/5.0/osgeo-live-5.0.iso" target="_blank">http://download.osgeo.org/livedvd/release/5.0/osgeo-live-5.0.iso</a><br>
>> >><br>
>> >> I'll just have to remember to stick to that naming convention<br>
>> when I'm<br>
>> >> making new versions<br>
>> >><br>
>> ><br>
>> > Correct me, when I'm wrong, I understood, that there is an<br>
>> naming convention<br>
>> > and if we use a pattern like the version replacement, we could<br>
>> change the<br>
>> > download.rst files in the way you summarized. So we don't have<br>
>> to care about<br>
>> > it in the future except the naming convention or uploading area<br>
>> will change.<br>
>> ><br>
>> > Give me a go and I can update the download.rst files ...<br>
>> ><br>
>> > Cheers,<br>
>> > Frank<br>
>> ><br>
>> ><br>
>> ><br>
>> Yes go ahead and make the change to create the links dynamically.<br>
>> Those<br>
>> are the correct naming conventions we intend to use. The url is<br>
>> unlikely<br>
>> to change in the foreseeable future aside from a new folder for each<br>
>> version (which is accounted for in your method).<br>
>><br>
>> Thanks,<br>
>> Alex<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Live-demo mailing list<br>
>> <a href="mailto:Live-demo@lists.osgeo.org">Live-demo@lists.osgeo.org</a><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/live-demo" target="_blank">http://lists.osgeo.org/mailman/listinfo/live-demo</a><br>
>> <a href="http://wiki.osgeo.org/wiki/Live_GIS_Disc" target="_blank">http://wiki.osgeo.org/wiki/Live_GIS_Disc</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Live-demo mailing list<br>
> <a href="mailto:Live-demo@lists.osgeo.org">Live-demo@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/live-demo" target="_blank">http://lists.osgeo.org/mailman/listinfo/live-demo</a><br>
> <a href="http://wiki.osgeo.org/wiki/Live_GIS_Disc" target="_blank">http://wiki.osgeo.org/wiki/Live_GIS_Disc</a><br>
<br>
_______________________________________________<br>
Live-demo mailing list<br>
<a href="mailto:Live-demo@lists.osgeo.org">Live-demo@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/live-demo" target="_blank">http://lists.osgeo.org/mailman/listinfo/live-demo</a><br>
<a href="http://wiki.osgeo.org/wiki/Live_GIS_Disc" target="_blank">http://wiki.osgeo.org/wiki/Live_GIS_Disc</a><br>
</div></div></blockquote></div><br>