Ticket #102 (new bug)

Opened 1 year ago

Last modified 1 year ago

pkgconfig file gets wrong filename

Reported by: mheiber Owned by: pygi
Priority: trivial Milestone:
Component: libburn Version: TRUNK
Keywords: pkgconfig, file naming, autotools Cc:

Description

Hey, I reported his bug a couple of weeks ago on the IRC yet I guess you either forgot about or didn't get to it yet. So, here it is again: right now, the .pc file libburn installs is named 'libburn-5.pc' which is kind of arbitrary since there are no five versions of libburn out there yet. I suppose it should stay at 'libburn-1.pc' until you're going for the 2.x release cycle (which I highly doubt will happen anytime soon).

Change History

Changed 1 year ago by scdbackup

I propose to use libburn-4.pc if such a step back is allowed.

We are now stably on SONAME 4. libburn-0.4.2 will produce libburn.so.4.7.0.

My only remorse is that we have to test any change before we can release it. libburn-0.4.2 is very much finished now. cdrskin binaries on 32 bit machine are already produced.

I would prefer if we could do the change in 0.4.3 and give it a few months of testing.

Unless there are strong reasons to make the change before the next Debian package gets produced. Are there ?

Changed 1 year ago by scdbackup

I can reduce my above objections to the question "Will it work for packagers."

It seems that the file has no consequences within cdrskin binary production.

So: what do the intended users of that file say ?

Note: See TracTickets for help on using tickets.