taskConcurrent Versions System - Tasks: task #4901, Reorganize download directories.

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #4901: Reorganize download directories.

Submitted by:  Derek Robert Price <dprice>
Submitted on:  Mon 07 Nov 2005 03:14:56 PM UTC  
 
Should Start On: Mon 07 Nov 2005 12:00:00 AM UTCShould be Finished on: Mon 07 Nov 2005 12:00:00 AM UTC
Category: NonePriority: 5 - Normal
Status: DonePrivacy: Public
Percent Complete: 0%Assigned to: None
Open/Closed: ClosedEffort: 0.00

Fri 11 Nov 2005 06:23:23 PM UTC, comment #3:

Okay, since there were no comments in the last few days, I've created the new directory structure on savannah. I haven't created any platform directories except x86-woe32 (and the symlink from x86-windows) & sparc-sunos, as examples. Please create new platform directories as needed.

I'm closing this issue.

Thanks,

Derek Robert Price <dprice>
Project Administrator
Mon 07 Nov 2005 09:13:31 PM UTC, comment #2:

> I beleive I would like to have the binaries also
> split between stable and feature.


Ok.

> Also, I suspect a need to distinguish binary releases on
> some operating systems as to 32bit or 64bit (solaris & hp/ux)
> and with GNU/Linux there will possibly be a dependence on
> which glib is being used. I do not know if the 32bit files
> should be mixed with the 64bit versions or not.


I assumed that could be part of the platform poriton of a host triplet when necessary: e.g. amd64.

> Could you come up with the concrete example pathnames you
> want to use for the next release of stable and feature as
> an example?


How about:

top/source/stable/1.11.22/NEWS
top/source/stable/1.11.22/README
top/source/stable/1.11.22/cederqvist-1.11.22.html.bz2
...
top/source/feature/1.12.14/NEWS
top/source/feature/1.12.14/README
top/source/feature/1.12.14/cederqvist-1.12.14.html.bz2
...

> top/binary/stable/unix/solaris/intel/9/cvs-1.11.22-sol9-intel-local.gz
> top/binary/stable/unix/solaris/sparc/9/cvs-1.11.22-sol9-sparc-local.gz
> top/binary/stable/unix/solaris/intel/10/cvs-1.11.22-sol10-intel-local.gz
> top/binary/stable/unix/solaris/sparc/10/cvs-1.11.22-sol10-sparc-local.gz
> top/binary/stable/unix/macosx/10.3/cvs-1.11.22.dmg


This looks like too much detail to me. The download area was actually organized like this once, but the sporadic nature of binary contributions meant that x86-sunos-9 might have a 1.11.19 and x86-sunos-10 might have 1.11.21. To find the latest one that worked on a given system often meant clicking around through several directories which might contain compatible binaries.

I would therefore prefer leaving off as much information in the path as possible, when possible. I also wouldn't expect us to get so many platforms that we'll have unusable clutter without subdividing UNIX. In this case, that would mean:

top/binary/stable/x86-sunos/cvs-1.11.22-intel-sunos-5.9.gz
top/binary/stable/x86-sunos/cvs-1.11.22-intel-sunos-5.10.gz
top/binary/stable/sparc-sunos/cvs-1.11.22-sparc-sunos-5.9.gz
top/binary/stable/sparc-sunos/cvs-1.11.22-sparc-sunos-5.10.gz
top/binary/stable/sparc-sunos/cvs-1.11.22-sparc64-sunos-5.10.gz
top/binary/stable/darwin/cvs-1.11.22-darwin-5.5.gz

The rule of thumb for creating a new directory should be binary compatibility, I think, ignoring backwards compatibility. So, even if Sparc Solaris 10 binaries won't run on Solaris 9, it is okay to group them with the Sparc Solaris 9 binaries since Solaris 9 binaries run on Solaris 10. Similarly for 64 bit binaries. IIRC, when Sparc went to 64-bit UltraSparc, the 32 bit binaries would still run on the 64-bit machines, so it would be okay to group the 64-bit and 32-bit binaries here.

> I don't know if the .zip files compatible with Microsoft
> Windows NT/2000/XP/2003 et all whould be listed under
> win32 or woe32...


Hrm. That's a good question. Though I'd like to get the woe32 thing across to a large number of people, not having a "Windows" or "Win32" directory would probably generate a lot of user confusion. How about an "x86-woe" directory with a symlink from x86-windows? If 32/64 bit binaries become an issue, we could use x86/64-woe. Do we need to worry about 95/98/ME separately?

> I am less certain what to do about the various GNU/linux
> distributions. Is it enough to create a .src.rpm and .i386.rpm
> for those that like RPMs (Redhat, Fedora, SuSE et al)
> and let the debian folks create their own packages?


If someone contributes them, I have no problem including them. Perhaps these do deserve RPMS, SRPMS, DEB, etc. subdirectories under x86-linux. We could leave it flat for now and reorg it again later if its starts looking too cluttered, though that may mean updating webpages with links, so maybe it is better to make those subdirs now?

> I believe we also need to discuss how to make available
> any customized development tools available... if we even
> still have any.


We don't have any currently, but what about a "top/development" directory for this when it is needed?

Derek Robert Price <dprice>
Project Administrator
Mon 07 Nov 2005 05:53:52 PM UTC, comment #1:

I beleive I would like to have the binaries also
split between stable and feature. It may be well
to also consider how other opensource binary packages are
released...

Also, I suspect a need to distinguish binary releases on
some operating systems as to 32bit or 64bit (solaris & hp/ux)
and with GNU/Linux there will possibly be a dependence on
which glib is being used. I do not know if the 32bit files
should be mixed with the 64bit versions or not.

Could you come up with the concrete example pathnames you
want to use for the next release of stable and feature as
an example?

top/source/stable/cvs-1.11.22/index.html
top/source/stable/cvs-1.11.22/NEWS
top/source/stable/cvs-1.11.22/README
top/source/stable/cvs-1.11.22/cederqvist-1.11.22.html.bz2
top/source/stable/cvs-1.11.22/cederqvist-1.11.22.html.bz2.sig
top/source/stable/cvs-1.11.22/cederqvist-1.11.22.pdf
top/source/stable/cvs-1.11.22/cederqvist-1.11.22.pdf.sig
top/source/stable/cvs-1.11.22/cvs-1.11.21-1.11.22.diff.bz2
top/source/stable/cvs-1.11.22/cvs-1.11.21-1.11.22.diff.bz2.sig
top/source/stable/cvs-1.11.22/cvs-1.11.22.tar.bz2
top/source/stable/cvs-1.11.22/cvs-1.11.22.tar.bz2.sig
top/source/stable/cvs-1.11.22/cvs-1.11.22.tar.gz
top/source/stable/cvs-1.11.22/cvs-1.11.22.tar.gz.sig
top/source/feature/cvs-1.12.14/index.html
top/source/feature/cvs-1.12.14/NEWS
top/source/feature/cvs-1.12.14/README
top/source/feature/cvs-1.12.14/cederqvist-1.12.14.html.bz2
top/source/feature/cvs-1.12.14/cederqvist-1.12.14.html.bz2.sig
top/source/feature/cvs-1.12.14/cederqvist-1.12.14.pdf
top/source/feature/cvs-1.12.14/cederqvist-1.12.14.pdf.sig
top/source/feature/cvs-1.12.14/cvs-1.12.13-1.12.14.diff.bz2
top/source/feature/cvs-1.12.14/cvs-1.12.13-1.12.14.diff.bz2.sig
top/source/feature/cvs-1.12.14/cvs-1.12.14.tar.bz2
top/source/feature/cvs-1.12.14/cvs-1.12.14.tar.bz2.sig
top/source/feature/cvs-1.12.14/cvs-1.12.14.tar.gz
top/source/feature/cvs-1.12.14/cvs-1.12.14.tar.gz.sig

top/binary/stable/unix/solaris/intel/9/cvs-1.11.22-sol9-intel-local.gz
top/binary/stable/unix/solaris/sparc/9/cvs-1.11.22-sol9-sparc-local.gz
top/binary/stable/unix/solaris/intel/10/cvs-1.11.22-sol10-intel-local.gz
top/binary/stable/unix/solaris/sparc/10/cvs-1.11.22-sol10-sparc-local.gz
top/binary/stable/unix/macosx/10.3/cvs-1.11.22.dmg

top/binary/feature/unix/solaris/intel/9/cvs-1.12.14-sol9-intel-local.gz
top/binary/feature/unix/solaris/sparc/9/cvs-1.12.14-sol9-sparc-local.gz
top/binary/feature/unix/solaris/intel/10/cvs-1.12.14-sol10-intel-local.gz
top/binary/feature/unix/solaris/sparc/10/cvs-1.12.14-sol10-sparc-local.gz
top/binary/feature/unix/macosx/10.3/cvs-1.12.14.dmg

I don't know if the .zip files compatible with Microsoft
Windows NT/2000/XP/2003 et all whould be listed under
win32 or woe32...

I am less certain what to do about the various GNU/linux
distributions. Is it enough to create a .src.rpm and .i386.rpm
for those that like RPMs (Redhat, Fedora, SuSE et al)
and let the debian folks create their own packages?

fwiw: My recollection is that the older layout was a bit
more chaotic with pathnames like this:

...
release/binary/unix/linux/RPMS/i386/cvs-1.11.8-cvshome.org.8x.1.i386.rpm
release/binary/unix/linux/RPMS/i386/cvs-krb-1.11.8-cvshome.org.8x.1.i386.rpm
...
release/binary/unix/osx/maccvs3.0/ChangeLog
release/binary/unix/osx/maccvs3.0/README
release/binary/unix/osx/cvs-1.11.2-OSX.bz2
release/binary/unix/sgi/cvs-1.11.8-SGI.gz
release/binary/unix/sunos/README
release/binary/unix/sunos/cvs-1.11.9-SUNOS-5.6.gz
release/binary/unix/sunos/cvs-1.11.9-SUNOS-5.8-i386.gz
release/binary/vms/cvs-1.9/vax-vms/cvs.exe
release/binary/vms/cvs-1.9.27/cvs-1.9.27.tar.gz
release/binary/win32/cvs-1-11-9.zip
...
release/feature/cvs-1.12.7/index.html
release/feature/cvs-1.12.7/NEWS
release/feature/cvs-1.12.7/README
release/feature/cvs-1.12.7/cederqvist-1.12.7.html.bz2
release/feature/cvs-1.12.7/cederqvist-1.12.7.html.tar.bz2
release/feature/cvs-1.12.7/cederqvist-1.12.7.pdf
release/feature/cvs-1.12.7/cederqvist-1.12.7.ps
release/feature/cvs-1.12.7/cvs-1.12.6-1.12.7.diff.bz2
release/feature/cvs-1.12.7/cvs-1.12.7.tar.bz2
release/feature/cvs-1.12.7/cvs-1.12.7.tar.gz
...
release/stable/cvs-1.11.15/index.html
release/stable/cvs-1.11.15/NEWS
release/stable/cvs-1.11.15/README
release/stable/cvs-1.11.15/cederqvist-1.11.15.html.bz2
release/stable/cvs-1.11.15/cederqvist-1.11.15.html.tar.bz2
release/stable/cvs-1.11.15/cederqvist-1.11.15.pdf
release/stable/cvs-1.11.15/cederqvist-1.11.15.ps
release/stable/cvs-1.11.15/cvs-1.11.14-1.11.15.diff.bz2
release/stable/cvs-1.11.15/cvs-1.11.15.tar.bz2
release/stable/cvs-1.11.15/cvs-1.11.15.tar.gz
...
unix/linux/SRPMS/cvs-1.11.6-cvshome.org.1.src.rpm

I believe we also need to discuss how to make available
any customized development tools available... if we even
still have any.

Mark D. Baushke <mdb>
Project Administrator
Mon 07 Nov 2005 03:14:56 PM UTC, original submission:

Hi guys,

Now that we have sftp access to the savannah downloads, I propose a directory structure similar to the old, old, FTP structure before Collab killed the ftp site:

top
|
|-sources
| |
| |-stable
| | |
| | \-VERSION
| |
| \-feature
| |
| \-VERSION
|
\- binaries
|
\-PLATFORM

Where VERSION represents multiple directories named after releases, such as 1.11.21, 1.12.13, etc., and PLATFORM represents multiple directories named after a host-os-version triplet, minus any parts of the triplet deemed unimportant (e.g. host is unimportant with the new OSX binaries that run on either PPC or x86). Files (other than READMEs, etc.) would only be placed in the VERSION & PLATFORM directories & docs would be in with sources in VERSION directories.

Derek Robert Price <dprice>
Project Administrator

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 5 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Fri 11 Nov 2005 06:23:23 PM UTCdpriceStatusNone=>Done
  Open/ClosedOpen=>Closed
Mon 07 Nov 2005 03:14:56 PM UTCdpriceCarbon-Copy-=>Added -unavailable-
  Carbon-Copy-=>Added -unavailable-
  Carbon-Copy-=>Added -unavailable-

Back to the top


Powered by Savane 3.1-cleanup1