Hi, On Fri, Oct 5, 2012 at 8:24 AM, Mathieu Malaterre <mathieu.malate...@gmail.com> wrote: > On Thu, Oct 4, 2012 at 1:41 PM, Sebastian Rahtz > <sebastian.ra...@it.ox.ac.uk> wrote: >> thanks, I need to think a little over the best way to do this. At the >> moment, I have a Jenkins >> instance which builds .deb files constantly, and I copy them into the >> tei.oucs.ox.ac.uk/teideb/ >> repository when we make a release. This works nicely. Does such a mechanism >> fit >> the Debian way of working, whereby the source system builds its own packages, >> rather than having a separate maintainer? > > As long as people (read: 'me') have access to the source debian/* > files this is fine (read: I can do the upload). Using git/cvs/svn is > not required. I simply need to see those debian/* files of yours. > >> Obviously I could upload the current state to mentors, and we could refine >> them >> to meet standards, but what is the best way of making that sustainable? > > You can upload them anywhere in the world, again as long as I have > access (dget URL) to those, this is fine.
Any update on this ? Thanks -- Mathieu -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ca+7wuszvx19k_uzz9tet-c4gz6+mz4exwi7rrpwweyp18xr...@mail.gmail.com
