[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: shared __init__.py file accross multiple python packages



On Fri, Apr 12, 2002 at 04:46:43PM +0200, Alexandre wrote:
> On Fri, Apr 12, 2002 at 04:30:14PM +0200, Jérôme Marant wrote:
> > On Fri, Apr 12, 2002 at 03:43:58PM +0200, Alexandre wrote:
> > > On Fri, Apr 12, 2002 at 03:21:04PM +0200, Jérôme Marant wrote:
> > >  
> > > >   Are the modules you're packaging part of the same source or are 
> > > >   they independant ?
> > > 
> > > They are independand. These are modules developed by my company, and our 
> > > policy is to have them live in a top level directory called 'logilab'
> > > under site-packages/, so it's not quite the same thing as the egenix
> > > packages.
> > 
> >   If there is not really something relevant for a dedicated common
> >   package, you can always add something like this in the postinst
> >   script of every logilab package:
> <snip> 
> 
> Looks nice. I'd have to do something in the postrm script of each
> package to check if there are still some packages in the logilab
> directory and remove the __init__.py file together with the logilab
> directory, right?

  Well, it is not necessary. It could be the user's responsibility
  to remove it since dpkg will tell you that is was not removed.

-- 
Jérôme Marant


--
To UNSUBSCRIBE, email to debian-mentors-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: