Re: build-essential / native-package-with-dash-version ?
On Tue, 28 Nov 2006 13:30:03 -0300, "andremachado" <andremachado@techforce.com.br> said:
> Hello, Many thanks for all suggestions. the
> http://php-java-bridge.sf.net states some specific minimal versions of
> gcc, make, automake, java, etc. So, I included these versions on
> debian/control file.
If the minimum versions are very old (e.g. if woody already meets the
minimum versions), you probably don't need to include those. It's
probably more trouble than it's worth.
> The remaining warnings can be seen at http://paste.debian.net/17466
> until nov 30th.
404: Not Found
> The native-package-with-dash-version warning is still without
> solution. I read again the Debian Policy (my english skill is bare
> minimum) and still not find how to rename package and use debuild
> -rfakeroot -uc -us to correctly build package.
Your package should not be a native package. It should consist of the
orig tarball, plus a diff.gz file. You are probably getting this
warning because when you built the package, it did not have access to
the original tarball. When you build your package, the original tarball
should be in the parent directory, with the name
[package-name]_[upstream-version].orig.tar.gz. So, in your case,
php-java-bridge_3.1.8.orig.tar.gz.
> Should I include version field in debian/control, while renaming
The version comes from debian/changelog.
> source directory only php-java-bridge, diverging from the original
> real source file? The real source from site is a bz2 file. I expanded
> it to a temp dir for compiling.
No, you should keep the source as pristine as possible. Probably the
best thing to do, IMHO, is to just bunzip it, and then gzip it.
> The configure-generated-file-in-source warning is there because source
> contains it.
Let upstream know about it. It may have been a mistake, and should be
corrected for their next version. Just make sure that it doesn't case
problems for your build, and you should be able to ignore that warning
for now.
> The package-contains-upstream-install-documentation is weird. I
> created a debian/docs file listing these files.
You don't need to include upstream's installation documentation, because
the procedure will be different for those installing from your package.
> The executable-not-elf-or-script I guess will continue. Jar, war,
> policy and stamp are generated by the compilation and are the results.
I don't know about whether jar files should be executable, but if they
shouldn't you should "chmod -x" them in your build process, after they
get installed.
--
Hubert Chan <uhoreg@debian.org> -- Jabber: hubert@uhoreg.ca
PGP/GnuPG key: 1024D/124B61FA http://www.uhoreg.ca/
Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA
Reply to: