Re: Compiled bytecode files location
Josselin Mouette <joss@debian.org> writes:
> Le mercredi 18 février 2009 à 13:33 +1100, Ben Finney a écrit :
> > I saw no response to Message-ID: <87skwceynw.fsf@benfinney.id.au>
> > on this forum, but would love to be convinced this will be fixed.
> > This is probably the last remaining issue keeping me with
> > ‘python-central’ for my packages.
>
> As I already said, there is no compelling reason to stay in /var,
Okay, I didn't see that when I looked back in the list archive.
> and this can be changed without too much breakage - I just couldn’t
> do that right before the lenny release.
Sure, I was only hoping for discussion at that time, not immediate
implementation of changes.
> I just proposed /usr/lib/pymodules/pythonX.Y instead. Do you think
> that location is suitable?
I think ‘/usr/lib/foo/’ is better than ‘/var/lib/foo/’ for program
libraries such as *.py and *.pyc, so to that extent it's a significant
improvement.
As for which directory names should be used under that hierarchy, I'm
currently neutral on most proposed systems I've seen. I'm not educated
enough on the issue of separation of these files to have an informed
opinion yet.
--
\ “Yesterday I saw a subliminal advertising executive for just a |
`\ second.” —Steven Wright |
_o__) |
Ben Finney
Reply to: