Re: Static linking without using a Built-Using attribute
Dear Nilesh,
Thank you very much for your help!
On 4/06/21 11:45, Nilesh Patra wrote:
> Hi Sébastien
>
> On Fri, 4 Jun, 2021, 2:15 pm Sébastien Jodogne,
> <s.jodogne@orthanc-labs.com <mailto:s.jodogne@orthanc-labs.com>> wrote:
>
>
> Adrian (Bunk) replied that "This is fixable with a +really version."
> [...]
> +really is used when version changes aren't consistent, or you need to
> downgrade.
>
> In this case, you would want to downgrade orthanc right?
To be fair, I am unsure whether I need to downgrade orthanc to 1.9.2, or
to make an additional operation on 1.9.3.
> So you should use this trick only for orthanc to my understanding.
In the hypothesis that I must downgrade from "orthanc-1.9.3+dfsg-1" to
"orthanc-1.9.2+dfsg-1", should I upload a release with version
"orthanc-1.9.2+really" to unstable?
Or should I name it "orthanc-1.9.2+dfsg-1-really"?
In practice, should I first sync my git repository with the tag
"orthanc-1.9.2+dfsg-1", do the modifications and upload to unstable,
then merge back my modifications in the mainline of the git repository,
and finally upload "orthanc-1.9.3+dfsg-2" to experimental?
> Also note that it is unclear to me what exact package should be put in
> "Built-Using". Is it "src:orthanc", "liborthancframework1", or
> "liborthancframework-dev",
>
>
> All libraries that you have statically linked against. See the binary
> packages that are relevant/contain the files that are being used for linking
>
> with or without version?
>
>
> With version, and more specifically with an exactly = relation.
> Please see the Debian Developers reference wherein it's clearly explained.
>From what I see in the Debian Developers reference [1], and from your
explanations, I guess I should use:
Built-Using: liborthancframework-dev (= 1.9.2+really)
Thanks again,
Sébastien-
[1] https://www.debian.org/doc/debian-policy/ch-relationships.html
Reply to: