[Slackbuilds-users] Built-in obsolescence

Robby Workman rw at rlworkman.net
Sat Jan 17 06:12:42 UTC 2009

On Fri, 09 Jan 2009 11:52:49 +0000
David Spencer <nobbutl at yahoo.co.uk> wrote:

> 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 :-/

So long as the deps build on 12.2, it's not really an issue, and since
upstream doesn't intend to release newer versions, I don't even see the
need for a special note.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090117/6958d204/attachment.asc>

More information about the SlackBuilds-users mailing list