526386 – Why should /var/cache be created at run-time?

Bug 526386 - Why should /var/cache be created at run-time?

Summary: Why should /var/cache be created at run-time?

Status:	RESOLVED DUPLICATE of bug 493154

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-10-21 22:46 UTC by Jeroen Roovers (RETIRED)
Modified:	2014-10-22 07:19 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jeroen Roovers (RETIRED) gentoo-dev

2014-10-21 22:46:00 UTC

net-misc/apt-cacher-ng-0.8.0 triggers:

 * QA Notice: This ebuild installs into paths that should be created at runtime.
 *  To fix, simply do not install into these directories.  Instead, your package
 *  should create dirs on the fly at runtime as needed via init scripts/etc...
 *
 *   var/cache
 *   var/cache/apt-cacher-ng

apt-cacher-ng is a proxy that caches tons of files there. It shouldn't matter whether the package installs that directory or whether it's done at run-time.

I have no idea how to begin to figure out why /var/cache/* shouldn't be a directory owned by a package. Why was this QA check added? Do we intend to introduce mechanisms that empty /var/cache?

Comment 1 SpanKY gentoo-dev

2014-10-22 05:17:17 UTC

bug 493154 contains documentation

Comment 2 Jeroen Roovers (RETIRED) gentoo-dev

2014-10-22 07:19:41 UTC


*** This bug has been marked as a duplicate of bug 493154 ***