Re: How to handle dependencies on unreleased packages?
On 02 Sep 2002 16:48:05 +0200 I've added the build-dep, but I don't get a versioned binary depend. Hmm. Come to think of it, why doesn't libd-i have the SONAME in the package name? Yes, this is a very badly packaged shared library. regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to handle dependencies on unreleased packages?
On Tue, Sep 03, 2002 at 09:47:22PM +0900, Junichi Uekawa wrote: On 02 Sep 2002 16:48:05 +0200 I've added the build-dep, but I don't get a versioned binary depend. Hmm. Come to think of it, why doesn't libd-i have the SONAME in the package name? Yes, this is a very badly packaged shared library. I was working on this a bit earlier today, and I will hopefully be able to commit some changes when I get home tonight. Regards, Martin -- Martin Sjögren [EMAIL PROTECTED] ICQ : 41245059 Phone: +46 (0)31 7710870 Cell: +46 (0)739 169191 GPG key: http://www.strakt.com/~martin/gpg.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
How to handle dependencies on unreleased packages?
I'm getting ready to commit my changes that make anna and main-menu share Packages-file parsing code. They do so by a function in libd-i. This means that if you want to build anna or main-menu after I've committed, you first have to build and install the new libd-i, which is still unreleased. Should I let anna and main-menu build-depend on libdebian-installer-dev (= 0.04) so you'll be forced to rebuild libd-i first? Is that enough, or should I add an explicit binary dependency on libdebian-installer (= 0.04) too? Regards, Martin signature.asc Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signeradmeddelandedel
Re: How to handle dependencies on unreleased packages?
On 02 Sep 2002 09:56:11 +0200 I'm getting ready to commit my changes that make anna and main-menu share Packages-file parsing code. They do so by a function in libd-i. This means that if you want to build anna or main-menu after I've committed, you first have to build and install the new libd-i, which is still unreleased. Should I let anna and main-menu build-depend on libdebian-installer-dev (= 0.04) so you'll be forced to rebuild libd-i first? Is that enough, or should I add an explicit binary dependency on libdebian-installer (= 0.04) too? Yes, both would be good. If you have the shlibs set properly, that should happen. I haven't looked at libd-i yet, so I cannot tell. regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to handle dependencies on unreleased packages?
mån 2002-09-02 klockan 13.16 skrev Junichi Uekawa: Should I let anna and main-menu build-depend on libdebian-installer-dev (= 0.04) so you'll be forced to rebuild libd-i first? Is that enough, or should I add an explicit binary dependency on libdebian-installer (= 0.04) too? Yes, both would be good. If you have the shlibs set properly, that should happen. I haven't looked at libd-i yet, so I cannot tell. I've added the build-dep, but I don't get a versioned binary depend. Hmm. Come to think of it, why doesn't libd-i have the SONAME in the package name? I haven't packaged any shared libraries so I'm not sure how it works... Regards, Martin signature.asc Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signeradmeddelandedel