>>>>> On Fri, 15 Jan 2010, Jorge Manuel B S Vicetto wrote:

> - From the alternatives, /var/lib/layman doesn't sound right.

The FHS (which we don't always obey, but in cases like this it's
useful as a guideline) says about /var/lib: "This hierarchy holds
state information pertaining to an application or the system. State
information is data that programs modify while they run, and that
pertains to one specific host."

IMHO that doesn't fit layman's usage case.

> If /var/cache/layman doesn't work,

It doesn't, since the data cannot be locally (i.e. off-line)
regenerated.

> what about /var/spool/layman instead?

Looks like it's the best location available in /var.

But by analogy, layman should store things in the same hierarchy where
the portage tree is, and that is under /usr. What was wrong with the
original location /usr/portage/local?

Ulrich

Reply via email to