Re: [DebianGIS] PostGIS status for debian unstable
On Thu, Feb 02, 2006 at 04:24:40AM +0200, alex bodnaru wrote:
> anyway, i will do the promised improvements, postgis will build and
> depend according to the packages in the current distribution, so after
> 8.0 will dissapear, postgis won't depend on it either.
>
> regarding the daemon builder, i'd kindly ask you to help reproduce the
> exact problem, as i intend to solve it properly.
Let me emphasis what is important here:
Any source package in Debian *must* have declared exactly what
build-dependencies it has -- what other packages (postgresql development
files, etc) it wants to be present during the build. Any package
*additionally* being present on the system where the package is built,
*must not have any influence on the results of the build*. If any
package would have, it must be added to Build-Conflicts, but it's much
preferred to instead make sure your package's build will not change
behaviour in the presence of such package (build-conflicts can be a
pain). Rationale is that any package must be able to recieve NMU's,
rebuilds, at any later time, and those NMU's should not suddenly
introduce other changes due to a violation of the above.
While building the source package prior to your manual upload, the
source package *must* declare exactly which result packages will be
built, that is, the exhaustive list of postgresql-X.Y-postgis packages
that will be built. While it is allowed to declare more packages than
that are built in debian/control (and hence Binary: of the .dsc), it is
discouraged, and no matter what, which packages exactly are built need
to be manually specified and not subject to change due to external
circumstances outside of human source package changes. This includes:
not subject to change during a simply repacking of the source package,
which includes running debian/rules clean. One is strongly urged to not
generate debian/control by automated means, only extremely few packages
have such an complexity that it would pay off.
Concluding from the above:
It is not allowed that, depending on what extra packages are
available on the system, more, less or different postresql-X.Y-postgis
packages are built. When new postgresql versions are added to Debian or
support for older ones dropped, postgis simply needs to have a new
upload with changes to the source package reflecting this fact.
Thanks,
--Jeroen
Member of FTP-Master team
--
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl
Reply to: