Well, pogma at least read this and fixed his package, did anyone else? Anyone else care? Is the shlibs field really that difficult to get? Everyone clear on this? I better not see people updating packages and doing it wrong. :)
Welcome in the real world :-) It's very normal, just consider the /sw/share/doc thingy I mentioned recently - the packages I listed explicitly apparently are all fixed now; but I didn't see any other package being fixed (OK I may have overlooked some, sorry, but my point should be clear). So, if you really want to get this fixed, you have to organize it. That means, either explicitly list which packages are affected, or provide a means to quickly fine out which ones are.
You may now say: "But that's not my job". And I'll reply: "You are right, but that's life, you gotta do things that are not really your responsibility if you want to get certain things done". Mind you, I do not say this is good... it's just how I perceive reality. :-/
After all, it's "not our job" to make sure packages are done right, either - we could just reject everything that's not up to our standard. Still on the package tracker we try to give people feedback on their submissions until they get it done. If we didn't do that, we would not have nearly as many "foreign" packages in the tree as we have now.
Also many people (e.g. me) didn't even add the shlibs fields to their packages, others did that. If these others did it wrong, that makes it that much harder for me to track down. Basically I would have to comb though my couple dozen packages for changes I didn't even made and verify if they are right. Even if I did, chances are high that I overlook something. Granted, the majority of packages do not have that many packages (a few have more than more, a few have about as much as me, but the majority has less than 10 packages).
Anyway, you will start caring when i fix "fink validate",
That would be very very much appreciated! Although it'd not be able to catch the sementical problems (people updating the dependency version in the Shlibs field incorrectly), but it'd catch some.
Which reminds me, I should extend the .deb validator to warn about versions occuring in /sw/share/doc/ subdirectory names. Anything we add warnings/errors about in "fink validate" makes our lifes easier.
and drm starts the rest of the shlibs project. :)
Well, we better get this sorted out before =)
Bye,
Max
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
