Mail Archives: geda-user/2012/02/15/05:00:45
Well ... I just discovered that the who-is-who of maintainers in Mageia
has some mixup - somebody else (whom I still have to find, but who knows
more about codeing than I do) had already created patches for the
problems with glib. I saw this quite late, because when the rpm package
did not run, I tried first of all to get my bearings right and started
to work with the (unpatched) tarball rather than digging into the rpm.
But even with these patches (the rpm package builds without errors),
gschem does not run - when gschem is launched by a user, it aborts with
error messages saying that gschem compiles (why does it?) something, but
fortunately cannot write into /usr/share/... The messages also suggest
to set some AUTO_COMPILE variable for which I cannot find any
documentation. Does that maybe ring a bell? Anyhow, the apparent
inconsistency between tarball and rpm package that initially made me
suspicious is now clarified.
I will now try to get the maintainership cleared - maybe I can just go
away and enjoy a couple of (less cold now) days of skiing and let the
other guy grind away.
One important question: when I checked last on the geda web-site, I saw
that 1.7.xx was still noted as not stable. Do you have a recommendation
on whether Mageia should be conservative and make 1.6.2 work in its rpm
package, or whether 1.7.2 (2 ?) is sufficiently stable to go into
production?
Something to verify on your side: are the - evidently necessary, given
the modified glib - patches already deployed in the code you are
maintaining ( I did not yet look at the code in 1.7.2)?
Juergen
- Raw text -