[Pkg-firebird-general] fb2 packages ready for testing

Grzegorz B. Prokopski gadek@debian.org
Mon, 28 Jun 2004 12:07:48 -0400

W li¶cie z pon, 28-06-2004, godz. 07:41, raseesink@hotpop.com pisze: 
> >>   I think FB2's build system should have been fixed so that it was
> >>   possible to use ./configure  --prefix=/usr
> >>   --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info 
> >>   plus possibly some extra options, and have all things by default
> >>   in the right places (FHS is the bible here)
> >I don't understand this, could you elaborate or give examples?
> http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1
> but mainly in:
> http://www.debian.org/doc/packaging-manuals/fhs/
> tells you were files should be.

This is the starndard way of specifying where binaries (/usr/),
dynamic data (/var/), shared static data (/usr/share) and others
should be installed.  I hoped in fb2 the default installation is not
"/opt-like" - like it was in fb1, but instead fb2 normally uses
autotools and installs things in (more-less) FHS-compatible locations
by default?

> The firebird configure script "lies" about options it has for the
> location of files try:
> ./configure --help
> after you have run ./autogen.sh

In general, we should not run ./autogen.sh on upstream "dist" tar
archives packages, unless it's really necessary to properly build
the package.

> I tried to use it when building my version but the settings don't seem to
> have any effect. Probably because interbase historically lived in /opt. I
> guess upstream should want to have this fixed too.

Agrh!  /opt is ugly!  AFAIR this was on TODO list for fb2 to kiss this
structure good bye (and it was 2 years ago...)

These symlink pools (which are not unique to FB debian packageS)
usually indicate projects that don't care about things like FHS and are
stuck in the 20th century...

			Grzegorz -disappointed- Prokopski

Grzegorz B. Prokopski      <gadek@debian.org>
Debian GNU/Linux           http://www.debian.org
SableVM - LGPL'ed Java VM  http://www.sablevm.org
Why SableVM ?!?            http://devel.sablevm.org/wiki/Features