openbravo-isv team mailing list archive

[Brian Thomason <brian.thomason@xxxxxxxxxxxxx>]

Hi Gorka,

Sorry I wasn't clear.  The source package name WILL need to change as it
will have to match the orig.  The binary package (what the user has to
download) can keep the same name.  So, the entry in the changelog and the
source package listing in control needs to match the orig.

I would recommend against putting lucid in it and rather somehow describe
what's different, and in this case it's the jdk you used to build against.
Your call though.

-Brian

On Sun, Apr 11, 2010 at 12:55 PM, Gorka Gil <gorka.gil@xxxxxxxxxxxxx> wrote:

> Hi Brian,
>
> Since the repositories of karmic and lucid share the orig files, we
> need to upload the orig with a different names.
>
> In one email you mentioned about the possibility of change the orig
> name, but we have tried with:
>
> sources: openbravo-erp-2.50MP-14
> orig:       openbravo-erp-lucid-2.50MP-14.orig
>
> and with "dpkg-buildpackage -S -sa" it builds a debian native package.
>
> If we use:
>
> sources: openbravo-erp-lucid-2.50MP-14
> orig:        openbravo-erp-lucid-2.50MP-14.orig
>
> it uses the orig directory but it builds the orig with name
> openbravo-erp_2.50MP-14.orig.tar.gz
>
> You mentioned that you sometimes change the orig without changing the
> binary filename, Could you please help us with this?
>
> Thanks,
> Gorka
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openbravo-isv<https://launchpad.net/%7Eopenbravo-isv>
> Post to     : openbravo-isv@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openbravo-isv<https://launchpad.net/%7Eopenbravo-isv>
> More help   : https://help.launchpad.net/ListHelp
>