linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@amulet.co.jp>
To: Michel Ddnzer <daenzerm@student.ethz.ch>
Cc: arcane@verinet.com, yellowdog-general@lists.yellowdoglinux.com,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: Need for Cross Platform Updates Distribution
Date: Mon, 19 Jun 2000 18:03:06 +0900	[thread overview]
Message-ID: <394DE1CA.509F24DC@amulet.co.jp> (raw)
In-Reply-To: 394DDB66.62A97110@student.ethz.ch


Michel D wrote
> Hollis Blanchard wrote:
> >
> > I look at that as trying to install an OS/2 binary onto a Windows box
> > (and then complaining that it doesn't work).
>
> Huh??? We are speaking about the same binaries for the same OS, but packaged
> in an incompatible manner.

Yes, and from two completely different companies.

Of course you usually *can* get a foreign rpm to install, it's just that
it's not unusual for it not to work with your system (or may break other
things in your system). Since neither company is testing their software
packages for compatibility with the other, this is not unexpected.

> > > Also, what's this about suse using /opt for kde and gnome? sn't
> > > /opt in the filesystem standard for commercial software only?
> >
> > It all depends on what "standard" you're using.
>
> Check out FHS (http://www.pathname.com/fhs/), which is an affiliated project
> of The Free Standards Group.

Ah, there it is. linuxbase.org needs to be a little better about
organizing their website it seems...

Getting back to /opt, it seems "The use of /opt for add-on software is a
well-established practice in the UNIX community." "Distributions may
install software in /opt, ..." blah blah blah.

It should be noted that this is just one standard, and on top of that a
standard only has strength if enough folks adhere to it. (Of course I
don't know of any others for Linux, and I think most distributions have
said they "will" adhere to it, whatever that means...)

> > I should also note that Debian packages also don't work well with other
> > distributions.
>
> But at least there aren't incompatible flavours of debs - you find a deb
> somewhere, you install it, it works.

Debian is of course a single organization (and honestly I don't know
anything about Corel or Storm or any compatibility issues there - isn't
Corel using an old glibc?). If only RedHat used RPM, you can bet any rpm
you could find would work.

-Hollis

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-06-19  9:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <394D2013.AAD184AB@golden.net>
2000-06-19  5:57 ` Need for Cross Platform Updates Distribution Olaf Hering
2000-06-19  7:33   ` Bryan Stillwell
2000-06-19  8:03     ` Steven Hanley
2000-06-19  8:19     ` Hollis Blanchard
2000-06-19  8:35       ` Michel Dänzer
2000-06-19  8:58         ` Olaf Hering
2000-06-19  9:03         ` Hollis Blanchard [this message]
2000-06-19  9:13           ` Michel Dänzer
2000-06-18 15:41 hendricks

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=394DE1CA.509F24DC@amulet.co.jp \
    --to=hollis@amulet.co.jp \
    --cc=arcane@verinet.com \
    --cc=daenzerm@student.ethz.ch \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=yellowdog-general@lists.yellowdoglinux.com \
    /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;
as well as URLs for NNTP newsgroup(s).