[Pkg-electronics-devel] gEDA 1.6.0 packages (and packaging)

[Peter Clifton]

On Wed, 2009-11-18 at 12:53 +0200, أحمد المحمودي wrote:
> Hello,
> 
>   Thanks for this effort !
> 
>   I started to look at your package yesterday, I have a few questions 
>   regarding debian/rules:
> 
> 1) What is this for:
> 
> PKG_CONFIG_PATH=$(CURDIR)/libgeda

Ah - that may not be required any more.. it was part of the trickery
required to build against a non-installed libgeda before we actually
fixed up the packaging properly.

Similarly, if there is anything which sets non-standard CFLAGS or header
search paths, they are no longer required.

> define find-libgeda
> PKG_CONFIG_PATH=$(PKG_CONFIG_PATH)
> endef

> 2) Why is the locale of libgeda installed in libgeda38 instead of 
> libgeda-common ?

I'm not 100% sure, but I think the reasoning is along these lines....
the locale "domain"(?) for lingeda38 _is_ "libgeda38".

It is not common to different libgeda versions - thus it is no defferent
to a lib* installing its locale files. libgeda-common was created
because the libgeda package installs some non-version-specific files.

In general, the fact that Debian split libgeda such that it can
(hopefully) co-exist with other libgeda soversions on the same machine
is probably a little overkill (since all geda pakages come from the same
source, and are updated at the same time) - although it isn't a problem.

> 3) Why is sch2eaglepos.sh removed from geda-gnetlist ?

I don't know - look to the debian/changelog of the old geda-gnetlist
package for that. (Actually - I just looked, and can't find any entry
referring to it - but this line was in the old geda-gnetlist package).

Perhaps someone one on the list knows, or you can check some debian
source-control of the package build-scripts (if such a thing exists for
these packages).

I simply copied the old rules from the separate packages and combined
into a unified set for the new single-tarball gEDA sources.


Best wishes,

Peter Clifton