Jerry James wrote:
On Mon, May 12, 2008 at 3:58 PM, Colin Walters <walters@xxxxxxxxxx> wrote:
Well, largely our "core" stack (and by this I mean comps) does not
(yet) have dependencies on many Java libraries. So there's not a big
deal swapping out say our objectweb-asm for JPackage's.
However, this is most definitely not a sustainable system in the long term.
I sort of view JPackage as just a specific instance of the
cross-distribution collaboration problem. Most distributions tend to
focus primarily on dependencies driven by desktop apps or their own
internal needs, but the general free software world is far larger than
that, even before OpenJDK opened up a lot of Java software to us.
So there are a bunch of Java packages that I use that I would like to
drive into *some* repository where they can get picked up and used by
others with similar needs. I've been driving towards Fedora so far.
What's a good long-term solution, then? Should I keep that up, focus
on JPackage, help figure out how the two are going to cooperate, ...?
It depends on who your target audience is. If it's Fedora, then just
get them into Fedora. If it's the Linux community, then get them into
JPackage and from there get them into Fedora.
-Toshio
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
