On 08/05/15 13:45, Stian Soiland-Reyes wrote:
On 7 May 2015 at 21:29, Andy Seaborne <[email protected]> wrote:
Suggestion:
Only produce the zip version so there is exactly one "source release" file
and so only one to check.
I think it's good to have both for longevity, and for the benefit of
OS distributions and automated builds, zip is after all a confusingly
defined format, and it is just a diff -ur to check their content is
the same.
It is a trade off - if there are two files, they both need checking or
some way to guarantee they have the same content.
But the source release isn't in an OS distribution or automated builds.
It's a one-time gold copy.
It's not like we will have a very large download page :)
(btw - could someone draft that? How is that done in Commons way? I
remember something to watch out for is chmod +x on the cgi-bin..)
What I wondered is why the proposed source distributions in
dist.apache.org are not simply byte-wise equal to the -src in
https://repository.apache.org/content/repositories/orgapachecommons-1095/org/apache/commons/commons-rdf-parent/0.1.0-incubating/
?
(and why does that folder contain bout -src and -source-release.zip?)
(Don't worry, the files inside it are byte-equal to the ones in the
proposed release archives - except that -source.zip also contains the
harmless examples/ folder)
Good question.
source-release is from the Apache parent.
