public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev]  Re: search functionality in emerge
Date: Mon, 24 Nov 2008 06:47:08 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.11.24.06.47.07@cox.net> (raw)
In-Reply-To: 396349.98307.qm@web31708.mail.mud.yahoo.com

devsk <funtoos@yahoo.com> posted
396349.98307.qm@web31708.mail.mud.yahoo.com, excerpted below, on  Sun, 23
Nov 2008 21:01:40 -0800:

> Why is a portage daemon such a bad thing? Or hard to do? I would very
> much like a daemon running on my system which I can configure to sync
> the portage tree once a week (or month if I am lazy), give me a summary
> of hot fixes, security fixes in a nice email, push important
> announcements and of course, sync caches on detecting changes (which
> should be trivial with notify daemons all over the place) etc. Why is it
> such a bad thing?
> 
> Its crazy to think that security updates need to be pulled in Linux.

Well, this is more a user list discussion than a portage development 
discussion, but...

For one thing, it's terribly inefficient to keep a dozen daemons running 
checking only a single thing each, each week, when we have a cron 
scheduling daemon, and it's both efficient and The Unix Way (R) to setup 
a script to do whatever you need it to do, and then have the cron daemon 
run each of a dozen different scripts once each week, instead of having 
those dozen different daemons running constantly when they're only active 
once a week.

IOW, it only requires a manual pull if you've not already setup cron to 
invoke an appropriate script once a week, and that involves only a single 
constantly running daemon, the cron daemon of your choice.

Now, perhaps it can be argued that there should be a package that 
installs such a pre-made script.  For all I know, maybe there is one 
already.  And perhaps it can be argued that said script, if optional, 
should at least be mentioned in the handbook.  I couldn't argue with the 
logic of either of those.  But there's no reason to run yet another 
daemon constantly, when (1) it's not needed constantly, and (2), there's 
already a perfectly functional way of scheduling something to run when 
it /is/ needed, complete with optional results mailing, etc, if it's 
scripted to do that.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  parent reply	other threads:[~2008-11-24  6:47 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23 12:17 [gentoo-portage-dev] search functionality in emerge Emma Strubell
2008-11-23 14:01 ` tvali
2008-11-23 14:33   ` Pacho Ramos
2008-11-23 14:43     ` Emma Strubell
2008-11-23 16:56       ` Lucian Poston
2008-11-23 18:49         ` Emma Strubell
2008-11-23 20:00           ` tvali
2008-11-23 21:20           ` Mike Auty
2008-11-23 21:59             ` René 'Necoro' Neumann
2008-11-24  0:53               ` tvali
2008-11-24  9:34                 ` René 'Necoro' Neumann
2008-11-24  9:48                   ` Fabian Groffen
2008-11-24 14:30                     ` tvali
2008-11-24 15:14                       ` tvali
2008-11-24 15:15                       ` René 'Necoro' Neumann
2008-11-24 15:18                         ` tvali
2008-11-24 17:15                           ` tvali
2008-11-30 23:42                             ` Emma Strubell
2008-12-01  7:34                               ` [gentoo-portage-dev] " Duncan
2008-12-01 10:40                                 ` Emma Strubell
2008-12-01 17:52                                   ` Zac Medico
2008-12-01 21:25                                     ` Emma Strubell
2008-12-01 21:52                                       ` Tambet
2008-12-01 22:08                                         ` Emma Strubell
2008-12-01 22:17                                           ` René 'Necoro' Neumann
2008-12-01 22:47                                             ` Emma Strubell
2008-12-02  0:20                                               ` Tambet
2008-12-02  2:23                                                 ` Emma Strubell
2008-12-02 10:21                                                 ` Alec Warner
2008-12-02 12:42                                                   ` Tambet
2008-12-02 13:51                                                     ` Tambet
2008-12-02 19:54                                                     ` Alec Warner
2008-12-02 21:47                                                       ` Tambet
2008-12-02 17:42                                                   ` Tambet
2008-11-23 14:56     ` [gentoo-portage-dev] " Douglas Anderson
2008-11-24  3:12 ` Marius Mauch
2008-11-24  5:01   ` devsk
2008-11-24  6:25     ` Marius Mauch
2008-11-24  6:47     ` Duncan [this message]
2009-02-12 19:16 ` René 'Necoro' Neumann
     [not found]   ` <5a8c638a0902121258s7402d9d7l1ad2b9a8ecf9820d@mail.gmail.com>
2009-02-12 21:01     ` Fwd: " Emma Strubell
2009-02-12 21:05       ` Mike Auty
2009-02-12 21:14         ` Emma Strubell
2009-02-13 13:37       ` Marijn Schouten (hkBst)

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=pan.2008.11.24.06.47.07@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-portage-dev@lists.gentoo.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