[Fink-devel] libdnet/libdnet1
While trying to build nessus-ssl, I came across an interesting problem with libdnet. The root of the problem is 10.4-transitional/stable libdnet installs the shlibs as libdnet-shlibs and unstable installs them as libdnet1-shlibs with no provides, or other compatibility tags. So, when I have unstable satisfying deps prior to unstable, and things depend on both libdnet and libdnet-shlibs, unstable libdnet is found, which depends on libdnet1-shlibs, and the stable libdnet gets pulled in to satisfy libdnet-shlibs, but they conflict. I solved this little problem by having everything that depends on libdnet-shlibs, depend on libdnet1-shlibs | libdnet-shlibs. This probably isn't the right solution. Rob --- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] libdnet/libdnet1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 we are working on this problem... - --- TS http://southofheaven.org/ Chaos is the beginning and end, try dealing with the rest. On 8-May-05, at 4:47 PM, Rob Braun wrote: While trying to build nessus-ssl, I came across an interesting problem with libdnet. The root of the problem is 10.4-transitional/stable libdnet installs the shlibs as libdnet-shlibs and unstable installs them as libdnet1-shlibs with no provides, or other compatibility tags. So, when I have unstable satisfying deps prior to unstable, and things depend on both libdnet and libdnet-shlibs, unstable libdnet is found, which depends on libdnet1-shlibs, and the stable libdnet gets pulled in to satisfy libdnet-shlibs, but they conflict. I solved this little problem by having everything that depends on libdnet-shlibs, depend on libdnet1-shlibs | libdnet-shlibs. This probably isn't the right solution. Rob --- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (Darwin) iD8DBQFCfqhr6wPs8J05MxMRAqigAJ9f4cnuPLON6mGpLmqGzQIcMmo4BQCgkuYv mUAUTylxVf/XTuBwM325oi0= =D5b+ -END PGP SIGNATURE- --- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] libdnet/libdnet1
On 2005-05-08, Rob Braun wrote: While trying to build nessus-ssl, I came across an interesting problem with libdnet. The root of the problem is 10.4-transitional/stable libdnet installs the shlibs as libdnet-shlibs and unstable installs them as libdnet1-shlibs with no provides, or other compatibility tags. So, when I have unstable satisfying deps prior to unstable, and things depend on both libdnet and libdnet-shlibs, unstable libdnet is found, which depends on libdnet1-shlibs, and the stable libdnet gets pulled in to satisfy libdnet-shlibs, but they conflict. Should be fixed now. It'd be helpful if next you've got a problem with a package, you could CC the maintainer(s). I at least would have gotten to your mail sooner. regards, crh pgp2yvTjUi1PS.pgp Description: PGP signature
Re: [Fink-devel] libdnet/libdnet1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yup that is the fix, you could use %v-%r though. - --- TS http://southofheaven.org/ Chaos is the beginning and end, try dealing with the rest. On 8-May-05, at 8:31 PM, Corey Halpin wrote: On 2005-05-08, Rob Braun wrote: While trying to build nessus-ssl, I came across an interesting problem with libdnet. The root of the problem is 10.4-transitional/stable libdnet installs the shlibs as libdnet-shlibs and unstable installs them as libdnet1-shlibs with no provides, or other compatibility tags. So, when I have unstable satisfying deps prior to unstable, and things depend on both libdnet and libdnet-shlibs, unstable libdnet is found, which depends on libdnet1-shlibs, and the stable libdnet gets pulled in to satisfy libdnet-shlibs, but they conflict. Should be fixed now. It'd be helpful if next you've got a problem with a package, you could CC the maintainer(s). I at least would have gotten to your mail sooner. regards, crh -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (Darwin) iD8DBQFCftUS6wPs8J05MxMRAvmmAKCNE6SODN/CxJ9w6CKWIsjTeWY1tQCfQ2vi HzgwV+tYsJWrx3hnlfQXPNY= =3cJo -END PGP SIGNATURE- --- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] libdnet/libdnet1
On 2005-05-08, TheSin wrote: Yup that is the fix, you could use %v-%r though. I've got a few things on my list to do with those packages. They're going to have to wait until next week after Thursday. When I'm done taking semester finals and also done presenting proposals for funding at work. Ah, the week of hell. How delightful it is. :-) crh pgpiEUv2uEEOd.pgp Description: PGP signature
Re: [Fink-devel] libdnet/libdnet1
TheSin wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yup that is the fix, you could use %v-%r though. To me, the section in the unstable libdnet SplitOff: Package: %N1-shlibs Conflicts: %N-shlibs Replaces: %N ( 1.5-2), %N-shlibs looks very much in contradiction with Fink shlibs policy. Why is this called %N1-shlibs when it provides the library with the same install_name as the previous %N-shlibs? Either the library is compatible with the older one, as its install_name and the higher compatibility number indicate, then the package name should be the same, or it is incompatible, then it should get a different install_name and no Conflicts/Replaces need to be there. What is the reason for this weird situation? Shouldn't the reason at least be mentioned in the info file? -- Martin --- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
