On 04/04/12 17:58, Bernard Li wrote: > Hi Stu: > > I am not too familiar with Debian and Ubuntu packaging but I just wanted > make sure you and Jeff are aware of each other's work. Obviously we do > not want any duplicated efforts. :) > > Going forward do you guys have any recommendations on how we can improve > the Debian packaging files within our repository such that anybody > downloading our official tarballs could build Debian packages out of it?
I've actually queried this on the Debian mentors list (on behalf of a number of projects I work with) - you can find some good responses to that question in their list archives for March, in particular: http://wiki.debian.org/UpstreamGuide Summing up the feedback: our primary focus (wearing the Ganglia hat) should be to produce a tarball that is as neutral as possible for all packaging systems. E.g. rather than trying to set CFLAGS stuff within configure, we should leave CFLAGS entirely in the hands of the packager. Second to that, it appears that Debian recommends - NOT keeping a `debian' directory (similar to an RPM spec file) in our `trunk' or `master' branch - NOT distributing such a directory in our tarball The pattern in the Debian world involves keeping a Debian branch, and only that branch has the debian/ directory. In many cases, the Debian branch is not even in the upstream repository: it is in a separate repository (e.g. on the Debian server alioth) ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
