Re: Validation failure for libpng15-32bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2/5/12 12:20 PM, Daniel Macks wrote:
> On Sun, 05 Feb 2012 10:27:57 +0100, Sjors Gielen 
> <[email protected]> wrote: 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?
> 
> I think you shouldn't rely on existing packages that don't seem 
> normal by fink standards and that have a ton of shims as an
> example of best-practice or even good/clever-idea inspiration:)
> Freetype219 *was* buried because we *had* had to contend with
> multiple libfreetype that all had the same libname, so we had to
> bury it in a package-specific way. It's pretty obvious from all of
> fink that /sw/lib/%n is in no way standard or blessed for normal
> packaging situations (nor does it align with the documented "wrong
> arch" layout for -64bit on i386). So *if* you're going to bury in
> a *pakcage*-specific subdir, you'd put *that* in 
> /sw/lib32/freetype219 or whatever the standard archlibdir is. dan
> 
> -- Daniel Macks [email protected]
> 
> 

%p/lib/i386 would be more along the lines of what we do for Type:
- -64bit, i.e. %p/lib/x86_64.

It's also what the gcc4N packages do already.  And the validator
accepts it without complaint.

- -- 
Alexander Hansen, Ph.D.
Fink User Liaison
http://finkakh.wordpress.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8u0tkACgkQB8UpO3rKjQ8kRQCfbX5Fi+7O75636sBkegDnq4ro
lWUAn1wfQ+/T+mCB1PTF/NTtk3Smmk17
=D/8t
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
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