[Gpe-list] WIki update
codehelp at debian.org
Wed May 7 08:58:41 CEST 2008
(Sending again as I signed the original and the Gpe-list doesn't accept
signed email! - please can that be fixed??)
On Tue, 2008-05-06 at 01:25 +0100, Graham Cobb wrote:
> Does anyone object if I replace the debian directories for the various
> components with the correct versions for building for Maemo?
By replace, do you mean that:
1. the released tarballs would still contain a debian/ directory but
containing Maemo stuff or
2. the Maemo files would only exist in RCS or
3. the Maemo files would be in some other directory?
Anything except option 1, please.
I can work around these problems but it would be easier for me if I
didn't have to replace files in debian/
> I know that the
> Debian GPE maintainer does not use these directories
(that'd be me) true - but what I need is not to have debian/ in any
released tarballs, no matter what that directory contains. It's not that
I don't use these directories, I have to replace all the files in those
directories and it makes packaging GPE in Debian a tad more work. I
don't have the option of telling the Debian tools to use some other
directory, (too many tools).
I don't mind what is done in RCS, what matters to me (and Debian) is
that none of the released tarballs contain a debian/ directory.
('debian/' is also case-sensitive, some Perl modules use Debian/ without
problems but I wouldn't advise that for GPE.)
I keep debian/ files in RCS for my own upstream projects - I just ensure
that debian/ is not included in EXTRA_DIST unless the package itself is
only useful in Debian.
(Emdebian also uses the debian/ directory for the embedded Debian GPE
> and I do not believe any
> other target uses them. And it might make it a little easier for anyone
> looking at Maemo development.
Including making Maemo available in Debian where the same problem arises
- whoever does Debian Maemo development does not want released tarballs
to contain a debian/ directory either, whether it is maemo-related or
Any other directory name is fine, just not debian/
BTW, I've come across a minor issue with gpe-soundserver where the
released tarball uses a version string that causes hassle for me.
The - in the version string causes the tarball to unpack to
gpe-soundserver-0.4-1/ instead of gpe-soundserver-0.4.1/ - I'm currently
repacking the tarball to solve this problem but it would be handy if the
next release could fix the release string to use 0.4.2 - all dots, no
dashes. I know it's very minor (and a trivial fix) but it is
surprisingly problematic. It wasn't worth a bug report but I thought I'd
mention it here.
More information about the Gpe-list