FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 06-17-2010, 01:36 PM
Ian Weller
 
Default libproxy bundles libmodman, upstream splits into two projects. what now?

Presently, libproxy bundles libmodman and includes it in the package.

Upstream split libmodman into a separate tarball, and then set up
libproxy to build off of a system version of libmodman if it exists
(otherwise it uses the version that is bundled with it).

Review request for the new libmodman package:
https://bugzilla.redhat.com/show_bug.cgi?id=603514
The packager will be sponsored by me, but I'm waiting for this package
to go through.

He also submitted this bug against libproxy:
https://bugzilla.redhat.com/show_bug.cgi?id=603517
Which asks the maintainer to upgrade to the version that can optionally
use the system version of libmodman.

And, of course, libmodman conflicts with all previous versions of
libproxy, because there are file conflicts.

Since both of these items basically depend on each other, where should
we go next?

--
Ian Weller <ian@ianweller.org>
() ascii ribbon campaign - against html e-mail
/ www.asciiribbon.org - against proprietary attachments
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 

Thread Tools




All times are GMT. The time now is 11:59 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org