From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: brobecker@adacore.com, dje@google.com, meadori@codesourcery.com,
gdb@sourceware.org
Subject: Re: Using Py_SetPythonHome
Date: Wed, 03 Oct 2012 18:40:00 -0000 [thread overview]
Message-ID: <83txub8kmf.fsf@gnu.org> (raw)
In-Reply-To: <20121003175343.GA14317@host2.jankratochvil.net>
> Date: Wed, 3 Oct 2012 19:53:43 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Doug Evans <dje@google.com>, Meador Inge <meadori@codesourcery.com>, gdb@sourceware.org
>
> please take this mail "with a grain of salt", although only a bit.
You too ;-)
> > that we should cater to the needs of people who do not provide
> > a distribution, but just a binary package.
>
> There are not any such people.
You are talking to them.
> > I still build a lot of software from sources,
>
> Binaries outside of package management no longer exists and they should be
> deleted ASAP if found as it is both a security hole and a too expensive
> software management issue.
On the contrary. I trust binaries I produced myself much more than
some package downloaded from somewhere.
> > Yes, it would be great if glibc dealt with it automatically for us.
> > But what about Solaris, HP-UX, IRIX, Windows? Right now, there is
> > no standard cross-platform way to deal with the problem. So each
> > project is on its own. Not ideal, but still a fact that we have to
> > deal with.
>
> Please withstand those few remaining years on those proprietary systems and do
> not try to reinvent GNU/Linux package management on top of them, that has been
> tried already uncountable times and it does not work. These proprietary
> systems are doomed, their missing package management is a part of this fate.
I'm afraid that's a pipe dream.
I really suggest that we do not base our design decisions on such
extreme assumptions.
next prev parent reply other threads:[~2012-10-03 18:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 23:23 Meador Inge
2012-09-17 17:07 ` Joel Brobecker
2012-09-17 17:46 ` Jan Kratochvil
2012-09-18 19:38 ` Doug Evans
2012-09-19 8:04 ` Jan Kratochvil
2012-09-21 15:37 ` Joel Brobecker
2012-09-21 15:44 ` Jan Kratochvil
2012-09-21 15:58 ` Joel Brobecker
2012-09-21 17:28 ` Jan Kratochvil
2012-10-02 13:09 ` Joel Brobecker
2012-10-03 15:13 ` Jan Kratochvil
2012-10-03 15:14 ` Jan Kratochvil
2012-10-03 15:39 ` Joel Brobecker
2012-10-03 17:44 ` Eli Zaretskii
2012-10-03 17:54 ` Jan Kratochvil
2012-10-03 17:57 ` Paul_Koning
2012-10-03 18:35 ` Eli Zaretskii
2012-10-03 18:43 ` Jan Kratochvil
2012-10-03 18:52 ` Eli Zaretskii
2012-10-03 19:03 ` Jan Kratochvil
2012-10-03 19:10 ` Eli Zaretskii
2012-10-03 19:54 ` Paul_Koning
2012-10-03 20:04 ` Jan Kratochvil
2012-10-03 20:11 ` Alfred M. Szmidt
2012-10-03 18:40 ` Eli Zaretskii [this message]
2012-10-03 19:26 ` Terekhov, Mikhail
2012-10-04 7:33 ` John Gilmore
2012-10-11 8:42 ` Jan Kratochvil
2012-10-11 14:54 ` Doug Evans
2012-09-21 15:55 ` Meador Inge
2012-09-21 16:01 ` Jan Kratochvil
2012-09-21 16:36 ` Doug Evans
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=83txub8kmf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=meadori@codesourcery.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 read-only IMAP folder(s) and NNTP newsgroup(s).