OpenBSD Journal

Expat moving to base

Contributed by merdely on from the movin-on-up dept.

Pierre-Yves Ritschard (pyr@) points out:

Marc Espie reminds us that expat moved from OpenBSD's X sources to the base system and pinpoints the impact for port builders

Read on for Marc's email to tech@

We finally activated expat in src/, and removed it from xenocara.

If you are using binary snapshots and packages, things will just update as they should, once new snapshots are available.

If you are building stuff from source, it is vital that you clean up your system. Most specifically, by removing the expat library from /usr/X11R6/lib.

Quite a few pieces of software will look in /usr/X11R6, using ld -L/usr/X11R6/lib

If you understand how ld works, you've got to realize it *will* prefer the version it finds there from the one under /usr/lib. Yes, even if it has a bigger major number.

(Comments are closed)

Comments

  1. By sthen@ (85.158.45.32) on

    mv not rm (unless you've already upgraded your packages from a package snap dated 19 oct or newer).

    Comments

    1. By Anonymous Coward (85.178.88.65) on

      > mv not rm (unless you've already upgraded your packages from a package snap dated 19 oct or newer).

      It was about time... ;-]

      Comments

      1. By Marc Espie (193.6.223.125) espie@openbsd.org on

        > > mv not rm (unless you've already upgraded your packages from a package snap dated 19 oct or newer).
        >
        > It was about time... ;-]

        Who the fuck are you ? I have absolutely no respect for anonymous idiots who just post these kind of comments from the sideline... especially repeatedly, as you seem to be doing.

        I don't think you have any idea how much work it takes to make OpenBSD work. Or if you have, you have a fairly interesting way to show it.

        So, just go away back to slashdot, or to whatever trashcan you crawled out from.

        Or at least post under your real name.

  2. By Daniel Ouellet (66.63.10.94) daniel@presscom.net on

    One thing I am curious about that I am not sure I understand fully the implication of it.

    Is this what was in the process for a long time meaning for example that the expat library, or folder if you want from apache as well can use this and be kill too? Or am I confusing two things here?

    I know a few years ago there was talk about killing the expat from apache as well, but not until the replacement was turn up in the system.

    Is that was we are talking about here?

    Thanks for putting light on this for me.

    Comments

    1. By Marc Espie (193.6.223.125) espie@openbsd.org on

      The only thing that's happened so far is that expat in src/ has been turned on.

      It's just basic engineering: both ports and xenocara need expat. Having expat in xenocara means some ports either duplicate the work (and hence you have two expats in the system), or you must install xenocara to have expat.

      So, moving expat up to src is the sensible thing to do.

      Nothing in base actually uses expat... apache uses expat-lite. Switching it to expat is probably going to be as much fun as doing anything in apache is, they have this tendency to take 3rd party software and modify just enough that getting back to the normal component is a complete nightmare.

      Comments

      1. By Daniel Ouellet (66.63.10.94) daniel@presscom.net on

        > Nothing in base actually uses expat... apache uses expat-lite. Switching it to expat is probably going to be as much fun as doing anything in apache is, they have this tendency to take 3rd party software and modify just enough that getting back to the normal component is a complete nightmare.

        Thanks for the reply. Make sense. As for apache, you are sure right! Doing a lots of cleanup on it maid me sick looking at it for a long time. May be a candidate for replacement by BSD license lighttpd one day. But that's a totally different subject.

        Thanks for putting light on the subject for me.

        Comments

        1. By Anonymous Coward (85.178.127.68) on

          > > Nothing in base actually uses expat... apache uses expat-lite. Switching it to expat is probably going to be as much fun as doing anything in apache is, they have this tendency to take 3rd party software and modify just enough that getting back to the normal component is a complete nightmare.
          >
          > Thanks for the reply. Make sense. As for apache, you are sure right! Doing a lots of cleanup on it maid me sick looking at it for a long time. May be a candidate for replacement by BSD license lighttpd one day. But that's a totally different subject.
          >
          > Thanks for putting light on the subject for me.

          I just would like to mention thttpd (in case a replacement gets ever considered). It's also under a nice license (BSD as far as I know) and has a sweet security history (+ small footprints in RAM and co).

          Comments

          1. By Brad (2001:4830:122b:3:216:41ff:fe17:6933) brad at comstyle dot com on

            > > > Nothing in base actually uses expat... apache uses expat-lite. Switching it to expat is probably going to be as much fun as doing anything in apache is, they have this tendency to take 3rd party software and modify just enough that getting back to the normal component is a complete nightmare.
            > >
            > > Thanks for the reply. Make sense. As for apache, you are sure right! Doing a lots of cleanup on it maid me sick looking at it for a long time. May be a candidate for replacement by BSD license lighttpd one day. But that's a totally different subject.
            > >
            > > Thanks for putting light on the subject for me.
            >
            > I just would like to mention thttpd (in case a replacement gets ever considered). It's also under a nice license (BSD as far as I know) and has a sweet security history (+ small footprints in RAM and co).

            thttpd is inferior to lighttpd in many many ways. It is not even close to being a replacement.

Latest Articles

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]