On 07/04/2018 18:49, Bruce Dubbs wrote:
On 04/07/2018 11:30 AM, Ryan Marsaw wrote:
On Sat, 7 Apr 2018, Pierre Labastie wrote:
Otherwise, configure errors out.
Amazingly, nobody seems to have noticed. So am I the only one?
You're not the only one :)
I'm constantly building pre-release versions of LFS/BLFS packages in
order to see what's changed, or what can potentially be build issues
down the line.
I've been building cryptsetup 2.0 since the first release candidate and
first noticed the json-c requirement right off the bat, but I wouldn't
have let the mailing list aware of this until the stable version
appeared. By the time it did, I'd forgotten about the extra
I think I might start keeping a list of packages for which new
dependencies are needed, and if nobody beats me to the punch I'll let
the mailing list aware of these new dependencies.
That would be very useful. From an editor's point of view, it is hard
to check every package update for changes for dependencies. We have
most packages already installed and if upstream adds something we
already have, it is easy to miss.
Agreed. When I first saw "dependency hell", I was wondering why. Now, I
cryptsetup fixed at revision 20052
Unsubscribe: See the above information page