MIME-Version: 1.0
In-Reply-To: <87fvy9kxr9.fsf@yoom.home.cworth.org>
References: <1365031678-25188-1-git-send-email-felipe.contreras@gmail.com>
	<87y5clte1j.fsf@zancas.localnet>
	<CAMP44s07KeL4uAChs3KFiqwcsCwWTvni6MzFGzXNeO7=sd6U6Q@mail.gmail.com>
	<87wqs4rsjm.fsf@zancas.localnet>
	<CAMP44s2RuAGjJV089swpjwG9i5X=sARPYve6XZPyK7X7QwZBDg@mail.gmail.com>
	<878v48om5u.fsf@zancas.localnet>
	<CAMP44s3x0m-KUN6aND71SHbBWz6S_23ZcQ-mcT+qxVtEdU+-5w@mail.gmail.com>
	<87a9oiw2pc.fsf@zancas.localnet>
	<CAMP44s3Qyc4mNx=MotX5vUKo-xpj0fj9Qmcoidpe3AKjbjV9_Q@mail.gmail.com>
	<871u9twrj2.fsf@zancas.localnet>
	<CAMP44s1DeLT76kTro85cm-vCAkiMUuYdcjFM3xQiUFtvXSVk_Q@mail.gmail.com>
	<87fvy9kxr9.fsf@yoom.home.cworth.org>
Date: Mon, 29 Apr 2013 13:30:14 -0500
Message-ID:
 <CAMP44s1MMSX1bdAhy=rEU4EvXBm0XznN4G+814QmB9-+KPZgbQ@mail.gmail.com>
Subject: Re: [PATCH] debian: package ruby bindings
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Carl Worth <cworth@debian.org>
Content-Type: text/plain; charset=UTF-8
Cc: notmuch@notmuchmail.org, David Bremner <bremner@debian.org>
Precedence: list

On Mon, Apr 29, 2013 at 1:16 PM, Carl Worth <cworth@debian.org> wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>> My hypothetical laziness is not the reason. It was at the strong
>>> insistence of Carl that things are organized this way.
>>
>> I still don't see why we need to do that. The notmuch project
>> shouldn't be bound to the debian project.
>
> I'm not sure what your specific question is here.
>
> My strong insistence was that the Debian packaging stuff, (like
> debian/rules), be hosted in the main notmuch repository.

Yeah, that's fine, but it's a different thing.

One thing is to host the debian packaging there (I think it should be
packaging/debian, otherwise the .spec should also be in the top
directory, but that's no big deal), and another thing is to bind the
live packaging.

So basically the notmuch project doesn't own debian/*, which I don't
think makes sense.

> If that were separated to a separate repository (or a separate branch),
> then nothing in the current situation would change. Your proposed
> change, (which is to debian/rules if I read it correctly), would instead
> be directed at that separate repository/branch.

I'm not proposing to so separate that directory to a separate
repository, I'm proposing to have a separate clone that is used for
the *live* packaging, that way the notmuch project can make changes to
debian/*, but only the package maintainer can merge them to the
'debian' specific branch, or repository in order to trigger the live
packaging.

Cheers.

-- 
Felipe Contreras