Please increase the sdcc (/home/groups/s/sd/sdcc/)
project web quota to 300000 k bytes.
Logged In: YES
As per section 6 (Acceptable Use) of our document on Project
web services at
you should not be hosting file releases via Project web.
Please remove such releases and host them via the File Release
Logged In: YES
I know that we are on the edge of allowed, but here is my
explanation why we are doing that.
The benefits sdcc snapshots are:
- Sdcc users have the possibility to get the most up-to-date
sdcc version. When a sddc user – actually a developer using
sdcc compiler – founds a bug in sdcc, he gets stuck and he
can't continue the work on his project. The response of sdcc
developers is usually very quick, and the defect is fixed in
few days or even in the same day. Sdcc snapshot makes it
possible for user to get the fixed version ASAP.
- Sdcc is built on many different operating systems and
platforms, which are usually not available to sdcc
developers. The developers have possibility to review the
build results and fix the problem which may be present only
on some platforms. This approach helped us many times to
found bugs, which were hidden on “mainstream” platforms, but
popped up on “more exotic ones” (32 vs 64 bit, little- vs
big-endian, different versions of compilers, libraries, ...)
- After the compilation the sdcc regression tests are
executed and the results are published on the sdcc snapshot
page. This helps us to discover the side effects of bug
fixing very soon: a new bug might be introduced by fixing
the old one...
The File Release is not an adequate alternative, because
this are not sdcc releases (the releases are already hosted
on File Release System), but daily snapshots, which are
available only for a week and then replaced with the newer
versions. As far as I know, the files can not be removed
from the File Release. There is also additional information
connected with each snapshot build: ClangeLog, regression
test results, which is difficult to achieve in File Release
System (at least not in such elegant way).
The proper solution wold probably be the “Snapshot service”
mentioned in section 6 (Acceptable Use), but in the next
paragraph is written that the service is not available yet.
You can also treat this writing as a Snapshot service request.
I hope that I explained the importance of sdcc snapshots for
the sdcc users and sdcc developers well enough. If you know
an alternative, please let us know. If not, please make an
exception and let us continue to work in the current way.
P.S.: I expressed my personal view, but I'm just one of many
sdcc developers. Other sdcc developers and users might have
different points of view and opinions.
Thank you for making our work possible,
Ok, I've increased the quota. Nice argumentation :)
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.