[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: OSCAR 10.12 has been packaged

Hi Peter,

On Tue, Jul 31, 2012 at 12:12:12PM -0400, Peter Hutten-Czapski wrote:
> The relevant numbers
> The latest release of Oscar is labelled 12
> its build 37 of the stable version of the branch
> and version 1.6 of the installation scripts
> I have tarred up the source that matches the binary and its at
> http://sourceforge.net/projects/oscarmcmaster/files/oscar_source_12-1.6.b37.final.tar.gz

I had a look into this and noticed that the tarball is something like
an archive of two separate Git repositories


For me this assembly of two different repositories just wrapped into one
tar file does not look like what I would call a *release* tarball.
Usually releases fo not contain any metadata from a VCS but rather
contain the pure source.  Moreover, the fact that the code and docs are
maintained in two separate repositories might give a hint that it makes
perfectly sense to also do tow different source and binary Debian
packages (for sure with proper Dependency relations set).

I wonder whether the Oscar project could do some versioned source
release containing the pure content of oscar_source/oscar without the
metainformation in oscar_source/oscar/.git and another versioned release
of the files in oscar_source/oscar_documents/ (also without .git) or if
both parts would be very closely connected also in one tarball but just
as a release and not a simple dump of a Git repository clone.

I also had a quick look into the binary JAR file issue and found 69
files that will need closer inspection.  IMHO for the moment it is to
hard to get rid of all these in one rush and so we probably need to go
to the non-free section of Debian.  In any case we need to make sure
that we assemble the licenses of these JAR files - some 'UNKNOWN'
strings in the file names are looking suspicious.

Kind regards



Reply to: