Re: Policy for .ph files in packages?

[Preston Smith <psmith@physics.purdue.edu>]

On Fri, Oct 19, 2001 at 11:17:49PM +0200, Michael Koehne (kraehe@copyleft.de) wrote:
>   - create a new package containing the *.ph files, and require the
>     with a 'Depends:' hint.
>   - test for existance in postinst, and create them on the fly.
> 

 The 'create on the fly in postinst' is the tactic that I chose, but in
 my package, I don't think that this is appropriate, for my package to
 create a ph files in other to make another one work. Of course, I'll ask
 the maintainer of libdevice-serialport-perl to add a creation line in
 his postinst again and see if I get a response this time.

 Might, though, a statement about what to do with .ph files in perl packages
 be a useful thing to have in the Perl policy? There's good information 
 about modules and such, but nothing of note for headers.

-- 
 Preston M. Smith <psmith@physics.purdue.edu>
 http://www.physics.purdue.edu/~psmith 
  "The only winner in the War of 1812 was Tchaikovsky."
         -- David Gerrold