From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Mark A. Hershberger" <mah@everybody.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: contributing Debian build scripts
Date: Thu, 24 Jun 2010 08:20:04 +0200 [thread overview]
Message-ID: <B9CAE1C3-9619-4A26-B506-B3064B98D9F5@gmail.com> (raw)
In-Reply-To: <87sk4daclx.fsf@everybody.org>
On Jun 23, 2010, at 7:21 PM, Mark A. Hershberger wrote:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> Can you please first elaborate what it would mean if we were to take
>> over the production of this package?
>
> Mosty, when releases are made, it would mean adding a changelog
> entry to
> the debian/changelog file, re-building the source package and then
> using
> dput to send the updates to Launchpad.net
>
>> Where would we have to submit it or put it up on the web so that it
>> would be found as an official package?
>
> I think the best way would be for me to create a group on Launchpad
> and
> then invite people to be a part of that group. Anyone in the group
> could submit packages to the package archive.
>
>> How does all of this work?
>
> The packaging scripts are kept in a debian subdirectory that can be in
> the same repository as org-mode itself or (as I've been doing) in a
> separate source repository. I've been using bzr-builddeb to create
> the
> packages since this allows me to maintain my packaging scripts
> separately from the upstream source.
>
> It looks like Launchpad has introduced support for automated daily
> builds and build recipes
> (https://wiki.ubuntu.com/DailyBuilds/BzrBuilder) since I last
> looked, so
> the work involved is probably going to be less than what I've been
> doing.
>
> After thinking about it a bit, I've created an Org-Mode group on
> Launchpad and requested an import of the Org-Mode git archive into a
> launchpad repository there so that it can be used in build recipies.
>
> I've also pushed my build scripts to that group so anyone who joins
> can
> contribute.
>
> So, next steps are: set up a daily build.
>
> Anyone interested in contributing is welcome to join:
>
> http://launchpad.net/~org-mode/
>
> Mark.
Hi Mark, thanks!
If I understand correctly, there is no action I need to take, right?
- Carsten
next prev parent reply other threads:[~2010-06-24 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 17:50 contributing Debian build scripts Mark A. Hershberger
2010-06-23 10:26 ` Carsten Dominik
2010-06-23 17:21 ` Mark A. Hershberger
2010-06-24 6:20 ` Carsten Dominik [this message]
2010-06-24 15:49 ` Mark A. Hershberger
2010-06-24 17:56 ` Carsten Dominik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B9CAE1C3-9619-4A26-B506-B3064B98D9F5@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mah@everybody.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).