Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Dec 2003 12:39:42 -0500
From:      Joe Marcus Clarke <marcus@marcuscom.com>
To:        Dmitry Sivachenko <demon@freebsd.org>
Cc:        Alexander Nedotsukov <bland@freebsd.org>
Subject:   Re: libsml2 & libxslt config files location
Message-ID:  <1072114782.756.15.camel@gyros>
In-Reply-To: <20031222140433.GA32655@fling-wing.demos.su>
References:  <20031222094622.GA99206@fling-wing.demos.su> <20031222114256.GA14823@fling-wing.demos.su> <20031222140433.GA32655@fling-wing.demos.su>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-49KAn0Bdak30HtXLqWfH
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2003-12-22 at 09:04, Dmitry Sivachenko wrote:
> On Mon, Dec 22, 2003 at 10:56:48PM +0900, Alexander Nedotsukov wrote:
> > Okay. Probably I missed you point here but I would say in general case=20
> > you can not update package w/o updating its config file if any.
>=20
>=20
> Most packages continue to work with old config files after upgrade.
>=20
>=20
> >=20
> > >These two files are the only exception: they cantain hardcoded version=
=20
> > >number of
> > >libxml2 and libxslt.
> > >
> > >It would be really nice to move them to some other place.
> > >Since their purpose matches gtk12-config closely, I propose /usr/local=
/bin=20
> > >for
> > >them.
> > >=20
> > >
> > We have {xml2,xslt}-config wich plays role similar to gtk12-config.=20
> > Those {xml2,xslt}Conf.sh files in qustion are *config* files. They=20
> > supposed to be included by various shell scripts. Yes they have .sh=20
> > suffix but look at their permissions, look at their content. I can coun=
t=20
> > on number of ports and most notable is portupgrade wich keep such=20
> > script-like config files under etc/ directory.
>=20
>=20
> If they are really config files, why do they contain version numbers of
> libxml and libxslt?!?  These are constants and can not be configured.
>=20
> If I upgrade those libraries and leave these files untouched, scripts you
> mentioned will continue to think we have an older version of these libs.
>=20
> I see no logic here.  What are these script which use {xml2,xslt}Conf.sh,
> provided that the same information can be extracted from {xml2,xslt}-conf=
ig?

They are used by gnome-config (which expects them in ${LOCALBASE}/etc).=20
Try it out:

gnome-config xml --cflags
gnome-config xml2 --cflags
etc.

Now, if you don't have gnome-config (part of gnomelibs), you should be
using pkg-config to obtain install info on packages such as libxml.  For
example:

pkg-config xml --cflags
pkg-config xml2 --cflags
etc.

In short, we cannot move the .sh files out of ${LOCALBASE}/etc as that
will break gnome-config, and a host of other applications.

Joe

>=20
>=20
> >=20
> > >_______________________________________________
> > >freebsd-gnome@freebsd.org mailing list
> > >http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
> > >To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.or=
g"
> > >=20
> > >
> >=20
> >=20
> >=20
> _______________________________________________
> freebsd-gnome@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
> To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org"
--=20
PGP Key : http://www.marcuscom.com/pgp.asc



--=-49KAn0Bdak30HtXLqWfH
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQA/5yxeb2iPiv4Uz4cRAgGrAJ0Xr00wP9EqD+lw6q+lR0XFqfwYngCdFB+P
UzLrHvkWZC3onXA4lAivekU=
=BdKt
-----END PGP SIGNATURE-----

--=-49KAn0Bdak30HtXLqWfH--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1072114782.756.15.camel>