dummy package?
Any policy that forces me to compile .py{c,o} object files in my postinst is
braindead. Then I also have to delete them in purge/postrm, and the
packaging system knows nothing about them.
The dummy package is there so that people already running tmda will get the
new version automat
On Wed, Feb 20, 2002 at 08:06:35AM +0100, Matthias Klose wrote:
> Adam McKenna writes:
> > On Wed, Feb 20, 2002 at 12:55:59AM +0100, Matthias Klose wrote:
> > > reopen 128531
> > > thanks
> > >
> > > > From: [EMAIL PROTECTED] (Adam D. McKenna)
&
ide of
the package management system.
--Adam
--
Adam McKenna <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
;s
impossible to support more than just the currently installed versions anyway.
Once a new version of python is added, the package will still need to be
updated or at least reinstalled to compile the modules for the new version.
--Adam
--
Adam McKenna <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
in python policy. If you want to
set forth a policy, it's usually a good idea to provide a rationale for it,
or at least say how things like this will be implemented. If the policy
needs updating, then please update it.
Thanks,
--Adam
--
Adam McKenna <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
5 matches
Mail list logo
