Am 18.08.2017 um 10:22 schrieb Ghislain Vaillant:
> On 16/08/17 21:29, Markus Koschany wrote:
>> I believe we should keep it simple and try to avoid using build profiles
>> except someone is really going to work on this stuff and files bug
>> reports and identifies key packages. If we decide to add
On 16/08/17 21:29, Markus Koschany wrote:
I believe we should keep it simple and try to avoid using build profiles
except someone is really going to work on this stuff and files bug
reports and identifies key packages. If we decide to add build profiles
we should do it in a consistent way though.
Am 16.08.2017 um 21:25 schrieb Ghislain Vaillant:
> On 16/08/17 19:47, Markus Koschany wrote:
>> Am 15.08.2017 um 11:18 schrieb Ghislain Vaillant:
>>
>> I never had to use build profiles because for me it was always something
>> related to bootstrapping Debian as a whole. This is actually the first
On 16/08/17 19:47, Markus Koschany wrote:
Am 15.08.2017 um 11:18 schrieb Ghislain Vaillant:
I never had to use build profiles because for me it was always something
related to bootstrapping Debian as a whole. This is actually the first
Java package I have seen where someone makes use of the buil
Am 15.08.2017 um 11:18 schrieb Ghislain Vaillant:
[...]
> My understanding so far:
>
> 1) DEB_BUILD_OPTIONS=nodoc: doc packages are built but left mostly empty
> 2) DEB_BUILD_PROFILES=nodoc: doc packages are not built at all
>
>> This is a more general tool
>> chain issue for Java packages. At th
On 14/08/17 23:03, Markus Koschany wrote:
Am 14.08.2017 um 22:45 schrieb Ghislain Vaillant:
On 14/08/17 21:11, Markus Koschany wrote:
2. I saw the no-doc build profile annotations in debian/control. Is that
something that you specifically need for libimglib2-java or is there
another reason?
Am 14.08.2017 um 22:45 schrieb Ghislain Vaillant:
>
>
> On 14/08/17 21:11, Markus Koschany wrote:
>
>> 2. I saw the no-doc build profile annotations in debian/control. Is that
>> something that you specifically need for libimglib2-java or is there
>> another reason?
>
> See
> https://www.debian.
On 14/08/17 21:11, Markus Koschany wrote:
Am 12.08.2017 um 17:02 schrieb tony mancill:
[...]
I spoke with Markus yesterday about libimglib2-java and so will wait to
hear back from him before starting on that one. Again *thank you* for
your patience, and for your contribution to Debian!
Hi,
Am 12.08.2017 um 17:02 schrieb tony mancill:
[...]
> I spoke with Markus yesterday about libimglib2-java and so will wait to
> hear back from him before starting on that one. Again *thank you* for
> your patience, and for your contribution to Debian!
>
Hi,
I have just reviewed libimglib2-java a
On 12/08/17 16:02, tony mancill wrote:
On Fri, Aug 04, 2017 at 04:11:07PM +0100, Ghislain Vaillant wrote:
On 04/08/17 15:40, tony mancill wrote:
On Fri, Aug 04, 2017 at 12:50:22PM +0100, Ghislain Vaillant wrote:
Two of the leaf packages are Imglib2 [1] and Parsington [2] for which I have
prep
On Fri, Aug 04, 2017 at 04:11:07PM +0100, Ghislain Vaillant wrote:
>
> On 04/08/17 15:40, tony mancill wrote:
> > On Fri, Aug 04, 2017 at 12:50:22PM +0100, Ghislain Vaillant wrote:
> > > Two of the leaf packages are Imglib2 [1] and Parsington [2] for which I
> > > have
> > > prepared an initial p
On 04/08/17 15:40, tony mancill wrote:
On Fri, Aug 04, 2017 at 12:50:22PM +0100, Ghislain Vaillant wrote:
Dear Debian Java Team,
I am undertaking the effort of packaging ImageJ version 2.x for Debian,
which requires the packaging of quite a few Java libraries as a result of
the modularization
On Fri, Aug 04, 2017 at 12:50:22PM +0100, Ghislain Vaillant wrote:
> Dear Debian Java Team,
>
> I am undertaking the effort of packaging ImageJ version 2.x for Debian,
> which requires the packaging of quite a few Java libraries as a result of
> the modularization of the code base.
>
> Two of the
13 matches
Mail list logo
