This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Bottom line, folding in subordinate shared library support to the upstream RPM 4.x release might take a while. So, the question becomes: can we move on to shared RPM development libraries (/usr/lib/librpmdb*.dll) without support for subordinate shared library support?
libz --\ libelf ---\____librpm----rpm.exe libdb ---/ beecrypt --/
librpm --\ libz ---\ libelf ----+ ----- rpm.exe libdb ---/ beecrypt --/
I've already done it (modified the 4.1/4.2 builds to use external shared libraries). The plan is to add rpm's enhancements to each of those packages. The only thing we need to do is convince CGF to merge the zlib patches, which I see as "harmless" additions anyhow, and we should be set.
There is no reason to distribute redundant dlls, especially since it sort of contridicts the point of using dll's in the first place.
I've already had one-on-one conversations with Jeff Johnson, and he's filled me in on the nitty-gritty. As I stated before, there's no rush and I think we can get shared lib support in the next version of rpm.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |