Comment # 14 on bug 1205096 from Atri Bhattacharya

(In reply to Dominique Leuenberger from comment #13)
> 
> * rsvg over inkscape
> 
> 
> Now, looking at inkscape vs rsvg-convert, this won't be a very easy anser to
> give:

It is, from the point of view of a packager who needs to test their builds
locally, and could do without downloading a ~100 MB+ worth of unnecessary cruft
when downloading one single-digit MB sized package will suffice. Ditto for each
obs-worker building the package.

It isn't just build chains that is in question here (although yes that too).

Anyway, my question to you is really more focused on whether it is allowed to
submit forks of packages that are already in Factory to get around
disagreements with the original package maintainer of the magnitude seen here
(obviously with the appropriate conflicts etc. baked in).

I mean, I have (IMO) several improvements to the package that I am now simply
unwilling to submit via obs://network/nextcloud-desktop or any other route that
goes via the original maintainer. I could either just let my changes die and
rot or submit as a new package.