Re: FHS location for locally-compiled bytecode (was: FHS location for Python libraries as locally-compiled bytecode)

2008-07-28 Thread Toshio Kuratomi
Floris Bruynooghe wrote: On Mon, Jul 28, 2008 at 10:12:42AM -0700, Toshio Kuratomi wrote: Quick question: Why is bytecode considered an alternate binary format? it is portable between architectures so it seems like it could also be a candidate for /usr/share. A related question, though, wo

Re: FHS location for locally-compiled bytecode (was: FHS location for Python libraries as locally-compiled bytecode)

2008-07-28 Thread Floris Bruynooghe
On Mon, Jul 28, 2008 at 10:12:42AM -0700, Toshio Kuratomi wrote: > Ben Finney wrote: >> Howdy all, >> >> A little while ago on debian-python, we discussed the location of >> system files that are executable bytecode, created by package >> management tools at install time, and how to comply with the

Re: FHS location for locally-compiled bytecode (was: FHS location for Python libraries as locally-compiled bytecode)

2008-07-28 Thread Toshio Kuratomi
Ben Finney wrote: Howdy all, A little while ago on debian-python, we discussed the location of system files that are executable bytecode, created by package management tools at install time, and how to comply with the FHS. Ben Finney writes: Josselin Mouette <[EMAIL PROTECTED]> writes: As f

Re: FHS location for locally-compiled bytecode (was: FHS location for Python libraries as locally-compiled bytecode)

2008-07-28 Thread James Westby
On Mon, 2008-07-28 at 15:38 +1000, Ben Finney wrote: > This issue applies just as much to other packages with byte-compiled > languages (e.g. Elisp bytecode, Java bytecode, etc.) so I'm raising it > on debian-devel. Hi, It seems that you entered the wrong address for this message, is that the cas

FHS location for locally-compiled bytecode (was: FHS location for Python libraries as locally-compiled bytecode)

2008-07-27 Thread Ben Finney
Howdy all, A little while ago on debian-python, we discussed the location of system files that are executable bytecode, created by package management tools at install time, and how to comply with the FHS. Ben Finney writes: > Josselin Mouette <[EMAIL PROTECTED]> writes: > > > As for the FHS arg