Re: Validation failure for libpng15-32bit
Sjors Gielen <[email protected]>
| Newsgroups | gmane.os.apple.fink.core |
|---|---|
| Message-ID | <[email protected]> |
Op 05-02-12 00:42, Alexander Hansen schreef: >>> How many of these packages do we think there are going to be? This is accomodating certain legacy things that can't be brought forward to 64bit, rather than providing a platform for cutting edge versions of packages getting ready for the future. >> >>> If there won't be many, the big change might not be worth the effort. > > Yeah, good point. I can see some more Wine dependencies going 32-bit for more support, and there might be some applications supporting only 32-bit (for example, because they are partly assembly-based). Though every package is different in this regard, so maybe the best middle-ground solution would be to add some instructions regarding this to the Fink manual -- it will make it easier for maintainers to adher to a standard we're defining here. By the way, about that standard: at the moment freetype219-32bit installs in /sw/lib/freetype219-32bit because the original freetype219 installs in /sw/lib/freetype219. Maybe I should move this to /sw/lib32/freetype219 too. What do you think? Op 04-02-12 19:58, Alexander Hansen schreef: > > I'd probably still argue for expanding libpng15-32bit to include > headers, and carry a Conflicts/Replaces libpng15. Not having any of > libpng15 installed when libpng-32bit is, and vice versa, seems to me > like it makes the separation between the 32-bit and 64-bit packages > more robust. Yeah, I've given it some more thought and I agree with you. I'll change the package. > a), if nobody objects to the addition. I'd call it an "enhancement" > rather than a "patch". Doing just this part is trivial. And trivial it was. "Enhancement" is attached ;-). Should I add bin32 too, maybe? > I tend to get quite excitable about packages that don't pass .deb > validation, because I had a Fink openssl release disable my entire > system in the pre-validator days by wiping my /var directory. This > isn't that bad. :-) Bah. I understand your sensitivity for validation failure now ;-) Sjors ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ fink-core mailing list [email protected] List archive: http://news.gmane.org/gmane.os.apple.fink.core Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-core
lib32.patch
(text/plain, 875 B)
diff --git a/perlmod/Fink/Validation.pm b/perlmod/Fink/Validation.pm
index c0b1fa7..8883ed3 100644
--- a/perlmod/Fink/Validation.pm
+++ b/perlmod/Fink/Validation.pm
@@ -1536,7 +1536,7 @@ sub _validate_dpkg {
my @bad_dirs = ( map "$basepath/$_/", qw( src man info doc libexec lib/locale bin/.* sbin/.* ) );
push(@bad_dirs, ( map ".*/$_/", qw( CVS RCS \.svn \.git \.hg ) ) ); # forbid version control residues
- my @good_dirs = ( map "$basepath/$_/", qw( bin sbin include lib opt share var etc Applications Library/Frameworks ) );
+ my @good_dirs = ( map "$basepath/$_/", qw( bin sbin include lib lib32 opt share var etc Applications Library/Frameworks ) );
# allow $basepath/Library/ by itself, but with nothing below it other than what we explicitly allowed already
# (needed since we allow $basepath/Library/Frameworks)
push(@good_dirs, "$basepath/Library/\$");
signature.asc
(application/pgp-signature, 259 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8uS6AACgkQAZBOHH9jUAn69QCeJuJqs/gfi4QIg1QZhgYQ1Y5/ +nwAoJ6cgmdPG9de2Rs9w/6Q0ypImfxA =m802 -----END PGP SIGNATURE-----