[gobolinux-users] Freshen 3.0.0

[Michael Homer]

On Thu, May 8, 2008 at 1:46 PM, Isaac Dupree <isaacdupree at charter.net> wrote:
> Michael Homer wrote:
>> Don't do that, then.
>
> I'll try not to, but I can't promise what I'll do by accident with
> automated scripts that just look at simulated results, with multiple
> terminal windows open, and others (e.g.  if a GUI ever called Freshen in
> the background...) :-)
A GUI should use libfreshen and disable caching - it can maintain its
own state for the duration of its execution, which is the problem the
short-term caching is designed to solve for a command-line
application.

It is possible in certain circumstances for it to fail; I suppose I
could work around that by appending the tty name to the cache file, or
something, but it doesn't seem worthwhile.
>> As I said, it excludes anything named "KDE-*". Even if it were
>> case-insensitive (which it isn't, through laziness rather than
>> design), "glib-" is not a prefix of "glibc". It is mostly intended for
>> the cases like KDE itself, where you don't want it accidentally
>> upgrading you to KDE4 but you also don't want to exclude all the
>> components explicitly.
>
> yeah, that mostly works. Sorry for misreading you. But still, the
> example of Linux (which is kernel), Linux-Headers etc., and the entirely
> unrelated Linux-PAM (which is PAM, I believe).  Maybe we should be more
> careful about how we use dashes in names then?  And is it possible to
> exclude Perl (the interpreter) without excluding all the Perl-* modules...
No, it isn't. I did see that as a potential problem, but weighed it
against the annoyance of the KDE4 recipes and opted for the works-now
solution. I can see a case for skipping a kernel compile but still
wanting to upgrade PAM, though, so I might have to extend it now
rather than later. I will have to think about how best to do that.
-Michael