Re: shlib symbolic link to optional lib in lib<foo>-dev ?
- To: debian-mentors@lists.debian.org
- Subject: Re: shlib symbolic link to optional lib in lib<foo>-dev ?
- From: Helmut Grohne <helmut@subdivi.de>
- Date: Thu, 30 Apr 2015 22:22:21 +0200
- Message-id: <[🔎] 20150430202220.GA8921@alf.mars>
- Mail-followup-to: debian-mentors@lists.debian.org
- In-reply-to: <20150315154447.GA5856@bobek.localdomain>
- References: <20150309004516.GB26918@bobek.localdomain> <CAKTje6GS2-=bowxQKdqWc=ZAhXJQBXPY991YUd_SQ0PRoiM1Lw@mail.gmail.com> <20150309094536.GB7004@bobek.localdomain> <CAKTje6Fg9wiaGd-FZtvm=98QapyGnC+DkNWbC5MAy1hdraPZgg@mail.gmail.com> <20150315154447.GA5856@bobek.localdomain>
On Sun, Mar 15, 2015 at 04:44:47PM +0100, Václav Ovsík wrote:
> I tried a bit different approach. The new src:ustr generate bin packages:
> libustr-1.0-1
> libustr-1.0-1-dbg
> libustr-dev
> libustr-doc
> Developer can switch debian/control (use debian/control.wdbg) a then
> generate:
> libustr-1.0-1
> libustr-1.0-1-dbg
> libustr-dev
> libustr-doc
> +
> libustr-debug-1.0-1
> libustr-debug-1.0-1-dbg
> libustr-debug-dev
You can use build profiles[1]. You can keep all of these packages in the
same control file and mark the -debug ones with
Build-Profiles: <extradebug>
and check for ifneq ($(filter extradebug,$(DEB_BUILD_PROFILES)),) in
debian/rules. That way those packages are only built when -Pextradebug
is passed to dpkg-buildpackage.
Even though the archive does not fully support build profiles yet, you
can use them already, because your use does not involve profiles in
Build-Depends.
Helmut
[1] https://wiki.debian.org/BuildProfileSpec
Reply to: