All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Neal P. Murphy" <neal.p.murphy@alum.wpi.edu>
To: netfilter-devel@vger.kernel.org
Subject: Re: libxtables backward compatibility
Date: Sun, 3 Jul 2016 18:43:41 -0400	[thread overview]
Message-ID: <20160703184341.4e0522b4@playground> (raw)
In-Reply-To: <alpine.LSU.2.20.1607032351450.3257@nerf40.vanv.qr>

On Sun, 3 Jul 2016 23:56:38 +0200 (CEST)
Jan Engelhardt <jengelh@inai.de> wrote:

> 
> On Sunday 2016-07-03 23:29, Neal P. Murphy wrote:
> >> On Sunday 2016-07-03 22:00, Neal P. Murphy wrote:
> >> 
> >> >Specifically, should programs linked to--and expecting to use--libxtables.so.7
> >> >work with versions libxtables.so.10 and libxtables.so.11? I suspect yes
> >> 
> >> Absolutely not. Never has been in any shared library system.
> >
> >(I begin to see why some products stay with a specific set of pkg versions for
> >longer periods of time: keeping one or two things updated can turn into a
> >full-time job updating all of the related pkgs.)
> 
> This is why anyone caring about their time is offloading automatable task to
> software, like openbuildservice.org does for me.

That would be a great service to be able to use.

Alas, Smoothwall isn't there yet; it doesn't use packages. Maybe some day. Regardless, I still have to manually update the build process when bumping gcc, glibc, binutils and similar utilities; LFS is a good guide, but it still takes a long time to figure out how to make those packages build. Never mind poring through the build logs to find which packages ignore "-m32 -march=i586" (there are plenty of x86 CPUs in use that don't have the CMOV instructions, thus i586 is required). And never mind finding all of a package's dependencies, and adding new ones to the build.

Neal

      reply	other threads:[~2016-07-03 22:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-03 20:00 libxtables backward compatibility Neal P. Murphy
2016-07-03 20:59 ` Jan Engelhardt
2016-07-03 21:29   ` Neal P. Murphy
2016-07-03 21:56     ` Jan Engelhardt
2016-07-03 22:43       ` Neal P. Murphy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160703184341.4e0522b4@playground \
    --to=neal.p.murphy@alum.wpi.edu \
    --cc=netfilter-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.