From: Mike Gran <spk121@yahoo.com>
To: Mark H Weaver <mhw@netris.org>, "Jose A. Ortega Ruiz" <jao@gnu.org>
Cc: "guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: summer of code ideas
Date: Mon, 7 Mar 2011 17:45:35 -0800 (PST) [thread overview]
Message-ID: <152070.84438.qm@web37906.mail.mud.yahoo.com> (raw)
From: Mark H Weaver <mhw@netris.org>
>To: Jose A. Ortega Ruiz <jao@gnu.org>
>Cc: guile-devel@gnu.org
>Sent: Monday, March 7, 2011 5:10 PM
>Subject: Re: summer of code ideas
>
>>"Jose A. Ortega Ruiz" <jao@gnu.org> writes:
>>> (use-modules (url://a-url.com library module #:optional a-rev-number))
>>
>> FWIW, i think this is a bad idea. It intermingles two concerns that are
>> othogonal, namely installing a package and using it.
>
>I very strongly agree with jao. Systems like this, e.g. Python Eggs,
>have been a major headache for distributions to deal with. Debian
>actually takes the time to disable this automatic downloading and
>installing functionality from their Python packages, and I'm glad for
>it. I am very security conscious, and the thought of software being
>automatically installed "on-demand" from untrusted sources when I run a
>program, or maybe even when I first use some particular functionality of
>that program, is very disconcerting.
I think people are conflating 'an idea' with 'the idea' here. The call was
for possible SOC ideas.
At my work, we sometimes operate this way: field engineers use client
programs that are rather like AJAX webapps. The head office updates a
server. It works for us.
I didn't suggest that for all time Guile must officially such a system.
Sheesh.
-Mike
next reply other threads:[~2011-03-08 1:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 1:45 Mike Gran [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-07 20:23 summer of code ideas Mike Gran
2011-03-07 21:25 ` Jose A. Ortega Ruiz
2011-03-08 1:10 ` Mark H Weaver
2011-03-07 19:51 Andy Wingo
2011-03-07 20:12 ` Noah Lavine
2011-03-07 21:33 ` Ludovic Courtès
2011-03-07 22:11 ` Noah Lavine
2011-03-07 22:27 ` Ludovic Courtès
2011-03-07 22:37 ` Noah Lavine
2011-03-08 13:00 ` Ludovic Courtès
2011-03-07 20:40 ` Noah Lavine
2011-03-07 20:46 ` Andy Wingo
2011-03-07 21:27 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=152070.84438.qm@web37906.mail.mud.yahoo.com \
--to=spk121@yahoo.com \
--cc=guile-devel@gnu.org \
--cc=jao@gnu.org \
--cc=mhw@netris.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).