On 04/19/2013 09:43 AM, Gerard Ryan wrote:
1. eclipse-wtp-common has been bundling a jar for a long time[0], and
I
tried to fix that, by deleting and rebuilding that jar using javac/jar
commands. Problem is I was using %{_libdir} to add a jar from
eclipse-platform to the classpath, and eclipse-platform is archfull but
this package is noarch. Is there a better solution? It's not my package,
so I don't want to do something like make it archfull if that's not
necessary.
If %_libdir is used only to build the jar then I don't see any problem
with using %_libdir in the spec file, even in noarch package.
2. I've proposed a patch for eclipse-wtp-servertools[1] a while back
that hasn't seen any activity.
Eclipse WTP packages in Fedora basically need to be build in the order:
common, servertools, sourceediting, webservices (I can't remember what's
after that, but the rest are mostly my packages, so I'll figure that out
when I get that far). The problem here is that the first three are not
mine, and the maintainer for servertools/sourceediting doesn't seem to
be very active at the moment, and I'm not going to try to update
sourceediting and propose a patch until I can build it against common
and servertools without having to hack unmerged packages into mock. I've
applied for acls on both in pkgdb, and I'm happy to spend time whipping
them into shape, since a significant percentage of my packages depend on
them directly.
You need to follow the policy for unresponsive maintainers[1]. After 3
weeks you'll be granted package ownership if the maintainer still
doesn't respond.
--
Mikolaj Izdebski
IRC: mizdebsk
[1]
https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers