Re: pruning ruby packaging in 10.9-libc++ tree

> On Sep 26, 2015, at 5:08 PM, Jack Howarth <[email protected]> wrote:
> 
> Daniel,
>      Any reason why we can't prune back the five different ruby packages in the 10.9-libc++ to just the most current ruby22 packaging? I only see a BuildConflicts on these packages in net/epic5.info and the legacy commented BuildDepends line in languages/swig.info and languages/swig302.info.
>               Jack

1.8 and 1.9 are no longer supported upstream so I have no problem dumping them. Not everything has been updated to 2.2 though, svn-swig-rb only supports up to 2.1 for example, so we should check what other things depend on the older ones first before killing them.

Daniel

------------------------------------------------------------------------------

_______________________________________________
Fink-devel mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJWBw2eAAoJEHIZ9WxpsAjhi64QAKofuixeHnHcMsTWMjj95s6d
4Jf0Fdzy+p114Z5ejne9y0ZZdz5dcex/ObiLsX8cGpLkt8m/t7OSx9byCokf/dyv
2B/qFTyol0ERzEH2r6BxL7P+serTJmKtDG6e2eBurAmqNvGtjSCRLgMESt+ocJ0j
XnNQI89Poxf+OBbfN1xNjLhImWaUqAvHFrZ8ufjMx6cbee1KyDJmmJoBWYkGlMoO
Oif1Q8VjgRaD2yIG/3uskjVwSHaDUbPYhcIeMzeUw2Vab3PWcH7Za+kQQjGbB/On
CgDiVoPngqGthqcH5dro2xIiRRwFQcEY8l4qywAjrVm6hBNoRjGTakdXjNLGKIXN
2n7C/TSLF1cnAig8XoCCteKGbZRtUCWmd1Qhi/upXt57nW+whrl4jISncPfvsx7X
QoMdB2rfMHVWq9j5FJwCym5TAr2ldhUB+7v3YttuM044q7lETz+hCXXZ/TFPqEfh
xHGpDUCFdP0h1LmEAsgLIbWpt7B9TGXBcn300ShuIhNs/U7Yfji0RWY54peHJVaP
gjbIs8DIdPNC9v0QApVXdbkodetbx94pLH4XXRCgOfCL/uYozlGG3Z93SADL0zdv
cuO31jhzVv5G441/gmDLL1xQmMCAgEKFberhyaqrRAkMw41U/T3VUdQKu0cv3nCL
RUBJSpH95AEWsY9BCFcs
=cuLm
-----END PGP SIGNATURE-----