[Slackbuilds-users] Built-in obsolescence

David Spencer nobbutl at yahoo.co.uk
Fri Jan 9 11:52:49 UTC 2009

JMRI is an app with two dependencies.  In both cases the dependent
packages, which are not currently available at SBo, must be very
specific versions which were obsoleted some time ago (rxtx-2.0-7pre2 and
javacomm-2.0.)  Upstream has indicated that there's no real prospect of
rewriting against newer versions.

How welcome would SlackBuilds for this, uhhh, idiosyncratic ensemble be?
 Obviously, the two obsolete packages would have to have prominent
warnings in the README and slack-desc.  Would that be good enough?

Sorry to hassle you all, but that's got to be better than just stinking
out the repository without asking :-/


More information about the SlackBuilds-users mailing list