Hi, On Thu, Oct 4, 2012 at 1:41 PM, Sebastian Rahtz <[email protected]> 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. > you can see our current state at > http://bits.nsms.ox.ac.uk:8080/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/; > but I need to start making source packages there too. Indeed, that would be the first step for me to start reviewing those. > PS there are currently 6 packages; I'll be withdrawing at least one of those, > if not two or three. I may > just end up with schema, doc and source ok Thanks much in advance ! -- Mathieu _______________________________________________ Debian-xml-sgml-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-xml-sgml-devel
