From: Diego Calleja <diegocg@teleline.es>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Announcing Binary Compatibility/Testing
Date: Thu, 14 Oct 2004 23:57:02 +0200 [thread overview]
Message-ID: <20041014235702.43586f70.diegocg@teleline.es> (raw)
In-Reply-To: <Pine.LNX.4.58.0410141129200.3897@ppc970.osdl.org>
El Thu, 14 Oct 2004 11:32:14 -0700 (PDT) Linus Torvalds <torvalds@osdl.org> escribió:
> No we don't.
>
> Yes, we "have the technology". But it's not actually used for libc (which
> is most of the problematic stuff), so we do not actually have library
> versioning.
is that a solvable problem?
quoting some dragonfly thread (whose aim is to implement something which
would solve that)
[...] via VFS 'environments', causes any particular package to see only
the dependancies that it depends on, and the proper version of said
dependancies as well. Multiple versions of third party apps that normally
conflict with each other could be installed simultaniously. The
packaging-system-controlled VFS environment would also hide everything a
package does not depend on, like other libraries in the system, in order
to guarentee that the dependancies listed in the packaging system are in
fact what the application depends on. There's no point in having a
packaging system that can't detect broken and incorrect dependancies or
we wind up with the same mess that we have with ports.
Diego Calleja (who wonders if this is feasible/worth of it)
next prev parent reply other threads:[~2004-10-14 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 22:16 Timothy D. Witham
2004-10-13 22:38 ` Timothy D. Witham
2004-10-13 22:39 ` Jeff Garzik
2004-10-13 22:55 ` Timothy D. Witham
2004-10-13 23:24 ` Robert Love
2004-10-13 23:36 ` Timothy D. Witham
2004-10-14 18:32 ` Linus Torvalds
2004-10-14 21:57 ` Diego Calleja [this message]
2004-10-15 19:49 ` Matthias Urlichs
2004-10-17 21:44 ` Kurt Garloff
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=20041014235702.43586f70.diegocg@teleline.es \
--to=diegocg@teleline.es \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®