Re: jedit_4.3.1+dfsg-1_amd64.changes REJECTED
- To: firstname.lastname@example.org, Debian Security <email@example.com>
- Cc: Michael Tautschnig <firstname.lastname@example.org>, Torsten Werner <email@example.com>, Alexander Reichle-Schmehl <firstname.lastname@example.org>
- Subject: Re: jedit_4.3.1+dfsg-1_amd64.changes REJECTED
- From: Gabriele Giacone <email@example.com>
- Date: Thu, 01 Apr 2010 00:30:52 +0200
- Message-id: <[🔎] 4BB3CD1C.firstname.lastname@example.org>
- In-reply-to: <20100318142739.GA32085@laptop165.dbai.tuwien.ac.at>
- References: <E1NrvsW-0000zv-Uu@ries.debian.org> <4BA10EEA.email@example.com> <4BA1DE7B.firstname.lastname@example.org> <email@example.com> <4BA22E19.firstname.lastname@example.org> <email@example.com> <20100318142739.GA32085@laptop165.dbai.tuwien.ac.at>
-----BEGIN PGP SIGNED MESSAGE-----
[ CC-ing d-security could give more feedbacks ]
a little summary:
I'm packaging jedit which uses a modified version of bsh (already in
Debian and team maintained). Building jedit against current Debian bsh
is not possible and uploading a new Debian bsh with jedit changes is not
a good idea because changes are only needed by jedit.
I looked for Debian binary packages which contain sources and I found
the following ones (maybe other exist)
mush-src (non-free, AFAIU binary redistribution not permitted)
qmail-src (non-free, AFAIU binary redistribution not permitted)
For example openjdk-6-source: source code is in both orig tarball and
openjdk-6-source binary package. This is a duplication, isn't it?
Regarding jedit, what about adding the creation of bsh-src binary
package, adding bsh-src to jedit's Build-Depends and applying jedit
patch at build time?
To take a look to the current jedit package which includes Debian bsh
tarball and applies jedit patch:
Thread on d-java: <4B858F27.firstname.lastname@example.org>
Thanks for your attention.
On 03/18/2010 03:27 PM, Michael Tautschnig wrote:
>> On Thu, Mar 18, 2010 at 2:43 PM, Torsten Werner <email@example.com> wrote:
>>> Hi Gabriele,
>> Hi Torsten,
>>> Gabriele Giacone schrieb:
>>>> But in order not to duplicate code, in which way could I get bsh sources?
>>> embedding our own copy bsh into jedit is duplication. Do we have a
>>> chance to avoid embedding bsh?
>> The ideal would be getting bsh _sources_ at build time treating them
>> as Build-Depends. Is it possible? Similar cases in the past?
> jedit requires modified bsh sources; could these changes be included in standard
> bsh and jedit just use bsh jars, or do these patches break standard bsh?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
-----END PGP SIGNATURE-----