Re: Review of fairsim, libjtransforms-java and libjlargearray-java
- To: Carnë Draug <carandraug+dev@gmail.com>
- Cc: debian-java@lists.debian.org
- Subject: Re: Review of fairsim, libjtransforms-java and libjlargearray-java
- From: Emmanuel Bourg <ebourg@apache.org>
- Date: Mon, 2 Oct 2017 17:22:56 +0200
- Message-id: <[🔎] 46b693cb-5a53-4fd6-9cc9-ed2f51f045bd@apache.org>
- In-reply-to: <[🔎] 8bf889ad-bd99-8f82-46d0-fbe9d3d8b937@debian.org>
- References: <CAPOrs_2CgGWYHHaTfWQu2m9-CT1G7mkj8urrBU7SOO5NVjut0A@mail.gmail.com> <2987ea94-ee49-aa93-e561-b0f126f95b12@debian.org> <CAPOrs_3NGpPhddHisGF_yMOHV+YvC9K0V2edo_a4=Rp-Rg875g@mail.gmail.com> <83b2d9c2-aad1-82c0-17b9-3571d350c978@debian.org> <CAPOrs_3i77KbifjLAaD1Go5T6OJG3b2h7obPg+GdTyJU+hgENg@mail.gmail.com> <5b892ff0-305c-5b38-915d-cabd545f4764@debian.org> <CAPOrs_1h=pwB6iUBVkw_CgsH-=DkBL=158cOec_eci08agmUrw@mail.gmail.com> <7287d657-8a2b-90dc-c2f4-093d0e148748@debian.org> <CAPOrs_2ch-hBnX8okoZf61cTAqHWN6n6Kzbn5VLToqW9OWTU5g@mail.gmail.com> <de8e111d-3cfb-e73d-e11c-6a72d360e228@debian.org> <CAPOrs_11jyLYv1_YFxnzG3--26faYBT=ZhNrPKrVvEQHsYA8JA@mail.gmail.com> <6e38b9de-89d6-71f5-aac6-0da36446c5cc@debian.org> <CAPOrs_3787t3+sDTAZk4ZUqcJJUL_H0AbSFPKJ7cBV_S+oU6Ug@mail.gmail.com> <59d87384-b94e-f662-716f-6b318b30d7fa@debian.org> <[🔎] 8bf889ad-bd99-8f82-46d0-fbe9d3d8b937@debian.org>
Le 2/10/2017 à 01:21, Markus Koschany a écrit :
> I also suggest to remove the --has-package-version flag from the *.poms
> files. There was a recent change in maven-debian-helper that
> automatically adds a versioned dependency to reverse-dependencies if one
> of their build-dependencies uses this flag. In my opinion in most cases
> this is too strict and not what you probably wanted.
Regarding the --has-package-version flag, my recommendation is to keep
it unless the version of the package doesn't match the version of the
pom. The versioned dependency added by maven-debian-helper is good for
ensuring consistent transitions to testing automatically (that is, if
libfoo-java requires libbar-java 2.0 but is ready before libbar-java for
a transition to testing, the versioned dependency holds libfoo-java in
unstable until libbar-java is ready to transition as well.).
Emmanuel Bourg
Reply to: