On Sat, Feb 15, 2020 at 12:57 AM Ola Bini <[email protected]> wrote: > > Hi, > > First - I apologize if this is the wrong medium for my questions. > > Me and my team have worked on a new FLOSS application in Golang, and > are now getting to the stage where we are thinking about making it > available in different package managers. The application is not > necessarily big, and doesn't have a large amount of > dependencies. About 4-5 of the dependencies have not been packaged > yet (and obviously not the application either). > > I have read the documentation and I think I understand the current > mechanics and practices for packaging Golang libraries and > applications. But my question is more about what is appropriate in > terms of process. Since the application is new, one alternative we > have considered is to first set up our own APT repository containing > the libraries and application, built according to the Debian > guidelines, and then, once it's been stable for a while, work together > with a Debian developer to get it all into the main repositories. > > (We are also planning on trying to backport the application for some > earlier Debian releases). > > Is this an appropriate way forward? Or is it suggested to simply start > packaging with the goal of getting the packages adopted by the Go team > immediately?
As a Debian Developer, I have no preference. I think you can do in the way which you feel convenient. -- Shengjing Zhu
