On Wed, Dec 24, 2008 at 06:42:30PM -0800, Danek Duvall wrote: > On Wed, Dec 24, 2008 at 08:41:30PM -0500, Mike Meyer wrote: > > In that case, the problem is with your packaging system. If python > > isn't supposed to be mucking around in python's library directories, > > then who is? > > Absolutely nothing. Once a package is installed to a directory under /usr, > /usr needs to be treated as read-only, as it very well may be mounted that > way. > > > pyc files are *not* some kind of compiled file you can use like elc or > > jar files. They're a caching mechanism used by the python vm/compiler > > combo to improve performance. > > If they're truly cache files, then they should go in a directory guaranteed > to be writable, such as something under /var.
Worse: it has to be writable by the user that runs Python. Perhaps we need a /var location for cached compilations and a service to do those compilations, either on demand or a priori. Nico -- _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
