This Time Self-Hosted
dark mode light mode Search

This is not the way to manage an Operating System

One would think that when you develop an Operating System, one of your objectives is to get it supported by as many software as you can, or at least you care. One of the things you might be trying is to make the developers of those software so that they can take care of that for you.

Unfortunately seems like FreeBSD people have not my same idea of how the thing has to be done. A simple way to check this is by looking at the nspr problem I found yesterday.

I got an emerge -e world running on Defiant after 6.2 update, and the only package to fail because of the update was dev-util/nspr. Why? Because a function was added in 6.2 series (getprotoname_r) that before was replaced by an in-line copy. The patch is trivial, and I submitted it upstream in Mozilla bug #354305 .

Now, just as an informative check, I wanted to look what ports did to that package, and gone on devel/nspr page … a similar patch to the one I’ve submitted already was present in the port since July! Version 4.6.1 of nspr. And never sent upstream.

Sigh.

By the way, this is yet another case where autotools beats the preprocessor tests: just AC_CHECK_FUNCS([getprocbyname_r]) and you’ll be fine.

Comments 3
  1. I am afraid that this is not only a problem for FreeBSD. There are also examples of this present in Gentoo Bugzilla.One that managed to hit me twice is [url=http://bugs.gentoo.org/show…]this one[/url] And this is just a random example. I’ve seen quit some bugzilla posts with solutions to known problem that simply don’t end up in the tree.

  2. This is not the same kind of problems. Patches that does not enter the tree are not at the same level than tested patch applied by a distribution and never sent upstream.Sending upstream the patches is the only way to make sure they are useful to someone.

  3. A patch that has been tested by a distribution should indeed be submitted upstream….I fully agree on that.However for me submitting patches to bugzilla feels very similar. The bug I link to simply breaks an emerge world and has done so for many months. Users have found a fix for it and other users tested it.If then those patches stay in bugzilla forever there is a big change that the next time you won’t bother submitting the things you fixed locally on your own PC.

Leave a Reply to FlameeyesCancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.