Bugs for Sorcery are reported here

[bugzilla-daemon AT metalab.unc.edu]

http://bugs.sourcemage.org/show_bug.cgi?id=6939





------- Additional Comments From seth AT tautology.org  2004-06-17 13:38 -------
The point was that we would have to carry a file around if it were in /var/tmp
for concievably forever on some boxes.  So it's one hack vs. another hack as 
far
as I can tell.

On the one hand, /var/tmp is supposed to get cleaned eventually, but not on
reboots, so I can see the point:

http://www.pathname.com/fhs/pub/fhs-2.3.html#VARTMPTEMPORARYFILESPRESERVEDBETWEE

"Although data stored in /var/tmp is typically deleted in a site-specific
manner, it is recommended that deletions occur at a less frequent interval 
than
/tmp."

"Site-specific" leaves it up to the package manager.  Dufflebunk chose not to
cruft a long-term hack for a more slightly inconveniencing short term hack.  I
can see the reasoning since we're trying to remove cruft from the sorcery
codebase.  So the current design is, I would say, consistent with the FHS.

If we required a cron daemon (but we don't) and cleaned /var/tmp of files 
older
than a month old (which might be good to have in an fcrontabs spell, for
example), we could safely put it in /var/tmp without worry, but we don't. 
Slightly more inconveniencing, but more control to the user both by not
requiring crontabs and not adding files that may hang around forever.  That's
what we're about, right?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.