|
|
Subscribe / Log in / New account

Debian, Rust, and librsvg

Debian, Rust, and librsvg

Posted Nov 18, 2018 10:51 UTC (Sun) by mjg59 (subscriber, #23239)
In reply to: Debian, Rust, and librsvg by Yui
Parent article: Debian, Rust, and librsvg

How do I get my application in the repositories for Debian Stretch?


to post comments

Debian, Rust, and librsvg

Posted Nov 18, 2018 14:59 UTC (Sun) by Yui (guest, #118557) [Link] (2 responses)

https://www.debian.org/doc/manuals/maint-guide/index.en.html

This is probably a reasonable starting point.

Debian, Rust, and librsvg

Posted Nov 18, 2018 16:31 UTC (Sun) by mpr22 (subscriber, #60784) [Link]

It seems to me that the point Matthew seems to be making has eluded you.

Debian stretch is the current Debian stable.

New packages are basically never accepted into Debian stable. (It is possible to imagine some exotic scenarios where they might be, but I imagine them being along the lines of "upstream for package Q currently in Debian stable has fixed a critical security vulnerability by a method involving the use of package P not currently available in stable and the Debian maintainers of Q do not have the labour resource available to develop their own fix".)

If you care enough to ensure that your program will work with 2- to 4-year-old versions of its dynamic library dependencies so that you don't have to drag in eleventy-one updated library versions that might actually break a stable system because the SONAME has been bumped, then once you've got it into unstable you can get it into the -backports repo for stable or possibly even oldstable - but that's officially not part of Debian.

Debian, Rust, and librsvg

Posted Nov 18, 2018 23:13 UTC (Sun) by mjg59 (subscriber, #23239) [Link]

I know how to add a package to Debian. I'm asking how to add a package to the current stable version of Debian in a way that ensures that it receives security updates. The backports process doesn't ensure this, and also restricts updates to versions that are available in testing - ie, if a dependency in unstable is blocked from testing for any reason, I'm not able to update the version in backports. Worse, backports policy is to only permit packages if there's established demand for them - if I have a new package, it's hard to demonstrate that.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds