Naming of a .pc file: package.pc vs package-version.pc
rdieter at math.unl.edu
Fri May 22 09:51:59 PDT 2009
Tollef Fog Heen wrote:
> ]] Rex Dieter
> | Tollef Fog Heen wrote:
> | > Not having co-installability means you might need to uninstall and
> | > install packages when you build different pieces of software. I don't
> | > really consider that a problem.
> | I consider it a problem. non co-installability is not friendly at all...
> | much preferable to have things "just work".
> I prefer to have my computers do work by automatically installing and
> uninstalling packages rather than having to do manual work on all
> reverse dependencies each time a package bumps its API. You appear to
> prefer the opposite. (Which is fine, but it comes down to a matter of
> preference and what kind of work you would like to do.)
I was simply responding to the "you might need to uninstall and install
packages when you build different pieces of software" comment.
My point: you either have full co-installability (of both runtime and
development environment) or you don't. Doing it half-way, ie. runtime
co-install ok but developer environment not, is just unacceptable in
this day and age (imo, and all that).
More information about the pkg-config