Re: What I'm thinking about in mainline fink right now

Alexander Hansen <[email protected]>
Newsgroups gmane.os.apple.fink.core
Organization Fink Core Team
Message-ID <[email protected]>
On 6/19/13 8:03 PM, Alexander Hansen wrote:
> 1)  I've finally smoothed some tuits down enough to work on
> https://github.com/fink/fink/issues/42 .  This is going use a similar
> methodology as the system-SDK packages, in that we're not going to have
> system-javaXY packages present at all for systems where one cannot
> possibly have that XY (e.g. system-java13 on Mountain Lion).  Having a
> virtual package present but not installed produces a confusing faux
> build process when installing something that depends on it, whereas not
> having an entry for the package gives a straightforward "package does
> not exist" message.
> Once I've got something that WorksForMe on different platforms, I'll put
> it in a branch of the main fink repository.
>

Meh, I just put it in master.  User-visible changes are:

1)  For people on 10.7 or later who have Oracle's Java-1.7.x installed, 
there will be system-java17* packages, plus the system-java and 
system-java-dev package will exist for people who don't have a legacy 
Apple Java installed, e.g. people who installed Mountain Lion after 
Apple dropped it.

2)  On 10.5/i386, system-java16* goes away because Java-1.6.x was 
distributed as x86_64 only for some reason there.


-- 
Alexander Hansen, Ph.D.
Fink User Liaison
My package updates: http://finkakh.wordpress.com/

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.