On Sat, Jul 25, 2015 at 7:14 PM, Michael Gilbert <mgilb...@debian.org> wrote: > On Sat, Jul 25, 2015 at 6:10 PM, James Montgomery wrote: >> As a wine-development user myself who has never done an official >> backport I wouldn't mind trying my hand at backporting. Is the wiki >> for BuildingFormalBackports[0] the best place to start? Also, if this >> is too big a beast to cut my teeth backporting I'd be interested in >> your thoughts as one of the wine maintainers. > > The backporting process itself should be nearly trivial for wine. After further research and testing, I totally agree and understand!
> The problem is more about that fact that whoever takes this on will need > to do uploads nearly every two weeks. So, unless you have DD or DM > upload rights, that won't be practical. If you would like to work > toward DM first, please consider contributing to the wine package > (solving bugs, proposing patches, etc.), which I will be happy to > review and possibly sponsor (wine-mono support would be nice). wine-mono, I've logged all the dependencies required, meticulously, and would now like ask you how Debian deals with such build systems where the build comes from the wine-mono script. As you're aware, wine-mono has the custom build script in the repository. Would the approach be to to decompose that build script through a series of patches for the Debian system? I cannot fathom that it would be acceptable to wrap the wine-mono build wrapper. What is the best approach in these situations? Thanks, James -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
