inline From: Bertrand Delacretaz <bdelacre...@apache.org<mailto:bdelacre...@apache.org>> Reply-To: dev <dev@sling.apache.org<mailto:dev@sling.apache.org>> Date: Monday, November 10, 2014 at 1:21 AM To: dev <dev@sling.apache.org<mailto:dev@sling.apache.org>> Subject: Re: Patch for quick & dirty debian package for sling launchpad standalone.jar
Hi Bruce, On Fri, Nov 7, 2014 at 7:08 PM, Bruce Edge <bruce.e...@nextissuemedia.com<mailto:bruce.e...@nextissuemedia.com>> wrote: Updated patch here: https://gist.github.com/bedge/b07793932aeb8929d81f Note, this is a peer module to builder rather than a submodule... Makes sense, though my preference would be to have this in contrib instead of the launchpad folder - what do others think? I'm fine with that. Also, I'll file a jira issue for tracking if that help make official. I just wanted to get a feel for the possibility of doing this before cluttering up the bug tracker with my wish list items. Also, the patch has: ...Maintainer: Bruce Edge <bruce.e...@nextissuemedia.com<mailto:bruce.e...@nextissuemedia.com>>... Shall we put dev@sling.apache.org<mailto:dev@sling.apache.org> here? Or will we get tons of automated mail if we do so? Good point. Most debian packages use an email addr that's tied to the upstream distro, but still funnels down to the actual maintainer so that the redirect can be changed as packages are handed off to different maintainers. Ideally something like a debian-maintai...@sling.apache.org that redirects to me for now, or, simply to the dev list. That way any influx of mail volume can be squashed by deleting the redirect. -Bruce (I've never created a Debian package myself, so mostly clueless) -Bertrand
