Loïc Minier <[EMAIL PROTECTED]> writes:
> On Thu, Jan 25, 2007, Øystein Gisnås wrote:
>> Is there a good way to let Maemo-specific packaging files coexist with
>> Debian unstable files in the upstream tree? Currently there is a
>> debian/ upstream, but it is Debian unstable specific. Btw tinymail is
>> not part of the official Debian Archive.
>
> I think the Maemo changes are additional control lines to e.g. have an
> icon in the list of installed apps. Perhaps you can simply generate
> debian/control from debian/control.in and rely on something like
> lsb-release to know when to insert the proper fields?
Evil. Don't change control at build time.
Beter to generate a debian/control.new from control.in and then fail
(with a helpfull message) if that differs from debian/control. Or
generally fail (with a helpfull message) whenever debain/control gets
changed. That way people can jsut restart the build if that was
intended.
> If it's also about changing a lot of build-deps / deps, then you might
> want to maintain a completely separate control file for maemo and move
> debian/control.maemo to control instead of sharing a common control.in.
I think the simplest thing is to branch. You might want to upload some
ix to stable-proposed-updates, security or testing-proposed-updates in
which case your changelog gets additional entries not present in the
unstable changelog and so on. A branch fits there perfectly.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
