*.py packaging, again
n3npq at mac.com
Thu Jul 14 14:57:40 CEST 2011
On Jul 14, 2011, at 8:05 AM, Tomasz Pala wrote:
> On Thu, Jul 14, 2011 at 07:19:34 -0400, Jeff Johnson wrote:
>> You also need to decide whether all compilations are on
>> the build system or after installation: there are different
>> I'd suggest that the problem needs to be solved on the install
>> not the build system as has been "traditionally" attempted.
> Do you want to skip them during repackage?
Do you actually use repackaged packages? For what purpose?
There are solutions here as well, depending on what is desired.
One can view side-effects like JIT'ed cached files as
either disposable and easily regenerated (in which case
the content should not be repackaged) or you can view
the JIT'ed cached files as stageful and persistent
(in which case repackaging should include the content).
All depends on POV and "expectations".
And since its highly likely that noone can state
the desired POV precisely, then
Have it your own way!
as an engineering solution would need to be attempted.
The two obvious resolutions to cached files are
Include them in repackaging.
Don't include in repackaging.
and that's essentially an if statement somewhere.
73 de Jeff
More information about the pld-devel-en