Details
-
Type:
Task
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: download.moodle.org
-
Labels:None
Description
After some email discussion about this. Here it's the one basic plan (feel free to comment/change) it:
1) Create one new download directory, say, http://download.moodle.org/4distro
2) Determine the list of libraries to delete from that special "4distro" packages.
3) Under that directory, store latest stable builds (WEEKLY!) in the form:
readme.txt (list of libraries being deleted in the package)
moodle_17_stable_20080522_1.7.4.tgz
moodle_18_stable_20080522_1.8.5.tgz
moodle_19_stable_20080522_1.9.1.tgz
moodle_20_dev_20080522_2.0dev.tgz
(nomenclature is: branch name + build date + release name)
4) Everybody will get those files as base for repackaging.
Some thoughts I think need consensus:
a) The decision about only MAJOR releases of WEEKLY ones. I think it's better to have there the WEEKLY ones because they are simply the best election to be packaged. And that way we'll ensure to maintainers to have there the best package ready to be downloaded.
b) I can imagine some potential problems about differences between linux flavours... what happens if we delete, say, adodb and there isn't adodb package for some linux distro? Do you think this is possible? Do we need to build different packages for each linux flavour? I hope no... but had to comment it here.
c) The moodle_17 and moodle_18 examples above are only one example. I think we must do this only for moodle_19 and above packages.
And that's all, feel free to comment/change anything (here or by email)... ciao 
Activity
- All
- Comments
- History
- Activity
- Source
- Test Sessions
a -> it would make most sense to have the final releases tarred to put into stable versions of the distros, while weekly builds are a nice to have though (debian, redhat and ubuntu usually dont upgrade major versions of packages in stable releases (which would require a full retesting of the dependency chain or even worse if the packages are on a CD a complete retesting of the CD build) while single fixes (and security fixes) often get backported)
b -> thats a responsibility of the package maintainer in a distro. she needs to care for the dependencies being available. if a lib is missing it should be packaged (beyond that users indeed can use the moodle upstream tgz and just unpack it if they desire to)
c -> totally agreed