Re: [rapicorn] Linking with librsvg (#4)
1 view
Skip to first unread message
Tim Janik
Dec 30, 2015, 5:14:58 PM12/30/15
to reply+00044d1f8c45043925647e99017a89c4fa0eb07...@reply.github.com, rapi...@googlegroups.com
Hey Rekado,
great to see you work on packaging!
I've spent some effort on packaging Rapicorn and Beast for Debian lately, hope that helps with your efforts. The results of that you can find here:
https://github.com/tim-janik/rapicorn/tree/master/debian
https://github.com/tim-janik/beast/tree/master/debian
About the librsvg bundling.
The reason for that are ways to resize SVG images in a non-standard way that could only be implemented by modifying librsvg.
But with some of the more recent SVG widget rendering efforts it looks like we might not actually *require* those resizing features, so there's a good chance that we can get rid of the embedded librsvg and still keep the widget rendering feature set in Rapicorn.
I don't remember off-head how hard it'll be to get rid of the code modifications to librsvg and am currently still at the CCC congress.
I guess I can look into helping with that early next year when I'm back home.
On 30.12.2015 20:37, rekado wrote:
>
> I'm trying to package Beast for GNU Guix and I noticed that rapicorn contains a modified copy of the librsvg sources. Is it possible to just build the additional files |svg.{cc,hh}| as |librcore_rsvg*| and link that with the upstream version of librsvg?
>
> It is frowned upon to bundle third-party code and package guidelines for many GNU/Linux distributions would only allow bundling in packages under extreme circumstances. I've been trying to modify the contents of |rcore/rsvg| in the manner described above, but have not yet been successful. It would be nice if rapicorn would provide such feature optionally.
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/tim-janik/rapicorn/issues/4>.
>
--
Yours sincerely,
Tim Janik
https://testbit.eu/timj/
Free software author and speaker.
great to see you work on packaging!
I've spent some effort on packaging Rapicorn and Beast for Debian lately, hope that helps with your efforts. The results of that you can find here:
https://github.com/tim-janik/rapicorn/tree/master/debian
https://github.com/tim-janik/beast/tree/master/debian
About the librsvg bundling.
The reason for that are ways to resize SVG images in a non-standard way that could only be implemented by modifying librsvg.
But with some of the more recent SVG widget rendering efforts it looks like we might not actually *require* those resizing features, so there's a good chance that we can get rid of the embedded librsvg and still keep the widget rendering feature set in Rapicorn.
I don't remember off-head how hard it'll be to get rid of the code modifications to librsvg and am currently still at the CCC congress.
I guess I can look into helping with that early next year when I'm back home.
On 30.12.2015 20:37, rekado wrote:
>
> I'm trying to package Beast for GNU Guix and I noticed that rapicorn contains a modified copy of the librsvg sources. Is it possible to just build the additional files |svg.{cc,hh}| as |librcore_rsvg*| and link that with the upstream version of librsvg?
>
> It is frowned upon to bundle third-party code and package guidelines for many GNU/Linux distributions would only allow bundling in packages under extreme circumstances. I've been trying to modify the contents of |rcore/rsvg| in the manner described above, but have not yet been successful. It would be nice if rapicorn would provide such feature optionally.
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/tim-janik/rapicorn/issues/4>.
>
--
Yours sincerely,
Tim Janik
https://testbit.eu/timj/
Free software author and speaker.
Reply all
Reply to author
Forward
0 new messages