Help getting started -- trying to build csound package

Felipe Sateler fsateler at debian.org
Mon Jun 11 00:59:10 UTC 2012


On Sat, Jun 9, 2012 at 11:15 PM, Forrest Cahoon
<forrest.cahoon at gmail.com> wrote:
> OK, I have a version locally committed to git which is working with
> the new upstream sources. I have

Great!

>
> * removed all 0xxx patches which have already been applied (some have
> not, and don't seem to be in the HEAD of upstream's git repo, either;
> that struck me as weird, but I left in all patches that would still
> apply).

Possibly some of them have only been applied in the csound6 tree.

>
> * added a 1xxx patch for a CMake file error, which I also posted to
> the csound dev list (although I don't know if it will be applied)

I saw the mail in the dev list, seems sensible enough.

>
> * updated debian/rules to change the cmake flag -DBUILD_NEW_PARSER to
> ON, as is now needed to compile.

Good.

>
> * added a 2xxx patch to the root level CMakeLists.txt which adds
> -DHAVE_LIBSNDFILE=1016 to the c flags.  The scons build has tests for
> the libsndfile version which are missing altogether in the cmake
> build. I couldn't figure out how to actually add the tests to the
> cmake, but since even debian stable has a version higher than the
> highest one the csound build looks for, I just added it as a
> debian-specific patch. This fixes debian bug #676145 I had reported
> earlier.

Its very likely that version 1.0.16 is not to be found anywhere now,
it was released in 2006. I'd propose that patch to the list too.

>
> The only thing that may yet need to be done is updating
> debian/copyright. I don't know what if anything actually needs to be
> done there. It doesn't look like there are any new files with non-free
> licenses.

Usually a diff between the different upstream/* tags gives enough
hints to know if there are new copyright notices to make. Given this
was a bugfix release, it is likely that no new files or copyright
notices are there.

>
> So, what's next? Do I get to push my changes back to alioth? How do I do that?

Yes! Use git push --tags origin master upstream pristine-tar
This is documented in the DevelopPackaging page of the wiki.

This way we can take a look at the changes.

-- 

Saludos,
Felipe Sateler



More information about the pkg-multimedia-maintainers mailing list