[Pkg-crosswire-devel] bibledit-gtk

[Dmitrijs Ledkovs]

On 20 December 2011 07:46, Teus Benschop <teusjannette at gmail.com> wrote:
> Hi team!
>
> Jonathan wrote (copied from another thread):
>
> ---
>
> Whether people use the CrossWire repositories or Teus' new one is up to
> them.  I'm not sure why Teus did not just ask that his packages be added
> to the Crosswire repo, having two places like this seems an unnecessary
> source of potential confusion to me.  That's something we can discuss
> independently.
>
> ---
>
> What happened it this: When setting up these source package recipes at
> [1] it just never occurred to me that these could also put their built
> packages into the stable CrossWire repositories.
>
> [1] https://code.launchpad.net/~teusbenschop/+recipes
>

You can even make the recipe owned by the team if you wish

> I do agree with you that it would be much better to put the built
> packages into the CrossWire repositories rather than in my own. I am
> willing to do this straightaway.
>

We even have to repos: developer testing for previews & stable
repository (which a lot of users use).

> But may we discuss one single things that now occurs to me. Yesterday
> bibledit-gtk-4.5 was released. It will soon land into my own
> repository at launchpad. Jonathan yesterday built bibledit-gtk-4.3 and
> put the packages into the CrossWire Developer Preview repository, and
> intends to copy them to the CrossWire Stable Packages repository. If
> two different version of bibledit-gtk land into the same repository,
> version 4.3 and version 4.5, will there be any interference between
> the two? Will one push out the other?
>

Please read Debian Policy about source package versions, binary
package versions and how both are kept in an apt-getable Debian
Archive.
And come back and ask if you still have questions or want additional
clarification.

In short it will be ok and by default higher version will be
installed. But you need to have correct dependencies between packages
using variable substitution preferably.

> Of course version 4.5 needs to be there in that repository because it
> is the newest software. And version 4.3 was needed for a special case
> that came up within SIL circles.
>
> Teus.
>

With regards,

Dmitrijs Ledkovs