From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Doug Evans <dje@google.com>,
Meador Inge <meadori@codesourcery.com>,
gdb@sourceware.org
Subject: Re: Using Py_SetPythonHome
Date: Wed, 03 Oct 2012 15:39:00 -0000 [thread overview]
Message-ID: <20121003153854.GC13994@adacore.com> (raw)
In-Reply-To: <20121003151244.GA22734@host2.jankratochvil.net>
> Show me any common GNU/Linux distro [...]
There lies the problem. You are being focused on distros, whereas I am
saying that we should cater to the needs of people who do not provide
a distribution, but just a binary package. This is why we disagree
so strongly. You need to understand that there are uses of Free
Software other than distribution-provided binaries.
It may be a lot less common today, compared to 15 years ago, but to
this day, I still build a lot of software from sources, and I move it
around from time to time.
Example: For GDB development, I build specific versions of the auto
tools, as well as flex, etc. I install them at a specific location
to start somewhere in my home directory. But then, the sysadmin asked
me to move it elsewhere because it takes too much room. Should I have
to recompile everything just because the world is now distro-centric?
Should every company out there that provides binary packages deal
with the problem on their own rather than share the feature just because
it isn't a necessary feature in distro-style binaries?
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.
> > Going back to the actual subject of this discussion, would it cause
> > a problem to call Py_SetPythonHome in your situation where everything
> > is static and installed at the default location?
>
> Yes, it is a problem because 99.9% of other Python-using packages behave
> differently.
With this reasoning, would people ever inovate?
--
Joel
next prev parent reply other threads:[~2012-10-03 15:39 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 [this message]
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
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=20121003153854.GC13994@adacore.com \
--to=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).