From: "Terekhov, Mikhail" <mikhail.terekhov@emc.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Using Py_SetPythonHome
Date: Wed, 03 Oct 2012 19:26:00 -0000 [thread overview]
Message-ID: <393A4D071DD24B45A370BEBB86AD05A22163337B7D@MX37A.corp.emc.com> (raw)
In-Reply-To: <20121003175343.GA14317@host2.jankratochvil.net>
Hi Jan,
You are living on another planet for sure.
Regards,
Mikhail
P.S. The same note about "grain of salt" applies.
> -----Original Message-----
> From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On
> Behalf Of Jan Kratochvil
> Sent: Wednesday, October 03, 2012 1:54 PM
> To: Joel Brobecker
> Cc: Doug Evans; Meador Inge; gdb@sourceware.org
> Subject: Re: Using Py_SetPythonHome
>
> Hi Joel,
>
> please take this mail "with a grain of salt", although only a bit.
>
>
> On Wed, 03 Oct 2012 17:38:54 +0200, Joel Brobecker wrote:
> > 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 need to understand that there are uses of Free
> > Software other than distribution-provided binaries.
>
> It is already a history.
>
>
> > 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.
>
>
> > to start somewhere in my home directory. But then, the sysadmin asked
> > me to move it elsewhere because it takes too much room.
>
> There do not exist any multi-user systems anymore. Each developer has her
> own
> virtual machine (in fact many of them), therefore sure with root access and
> with proper normal automatic package management there.
>
>
> > Should I have
> > to recompile everything just because the world is now distro-centric?
>
> Nobody is compiling software, this is happenning automatically in build
> farms.
>
>
> > 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?
>
> There is no problem, all files and their locations are under the control of
> package management of each GNU/Linux distro.
>
>
> > 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.
>
>
> > > > 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?
>
> That is a great idea. Packaging rules changes get proposed and discussed
> first at:
> http://fedoraproject.org/wiki/Packaging_Committee
> Or sure an appropriate body in some other major GNU/Linux distro featuring
> qualified people who can contribute to your idea.
>
>
> Thanks,
> Jan
next prev parent reply other threads:[~2012-10-03 19:26 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
2012-10-03 19:26 ` Terekhov, Mikhail [this message]
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=393A4D071DD24B45A370BEBB86AD05A22163337B7D@MX37A.corp.emc.com \
--to=mikhail.terekhov@emc.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.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).