On Mon, Mar 26, 2012 at 11:20:46AM +0200, Olivier Sallou wrote:
> this mail is primarly targeted to Andreas, but if someone has an
> opinion....
> upstream author of licensed issue file in JLAPACK agreed to change its
> license to a compatible one.
Uff. Good to know!
> However, as upstream code has been modified in JLAPACK software, I must
> reintegrate modifications made by JLAPACK team in upstream code.
> This is fine but I cannot patch it (would mean source code is not
> licensed compliant), so I have to remove impacted file and provide it
> myself via debian dir.
Fine for me.
> As orig source code has to be modified, and as there is no tarball to
> download (only CVS), I wonder if it would make sense that I fork the
> upstream code, apply modifications on licensed file and provide a source
> tarball myself.
This is fine as well. You need to write a get-orig-source script
anyway. It somehow needs to create what we afterwards call orig.tar.gz.
> Upstream code has not been modified for 4 years now, so we can think it
> is freezed and would not cause issue to fork it.
ACK.
> What do you think ?
Do whatever you would consider:
a) transparent enough (=reproducible via script)
b) makes you the least trouble
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120326113119.ge16...@an3as.eu
