Well, yes but...

Because it may be difficult to remove/replace this package with another
without having to change Xastir source code, it may be something the
development team will have to do, rather than the package maintainers.

On Mon, Mar 14, 2016 at 5:21 PM, David Flood <[email protected]> wrote:

> So it really isn't an Xastir bug, it's a Debian *Magick packaging bug..the
> maintainers of those two ecosystems need to update their packages to remove
> the Jasper dependency.
>
> <begin snark>
> And since Debian has been absorbed by the Borg Collective that is systemd,
> another option would be to wait until systemd takes over all the *magick
> functions and switch to that.
> <end snark>
>
>
>
> -----Original Message-----
> >From: David Ranch <[email protected]>
> >Sent: Mar 14, 2016 3:30 PM
>
> >The Xastir source code has dependencies that link to it.. specifically
> >GraphicsMagick / ImageMagick
>
>
> _______________________________________________
> Xastir mailing list
> [email protected]
> http://xastir.org/mailman/listinfo/xastir
>



-- 
Curt, WE7U
http://wetnet.net/~we7u
http://www.sarguydigital.com
_______________________________________________
Xastir mailing list
[email protected]
http://xastir.org/mailman/listinfo/xastir

Reply via email to