Re: policy concerning files used by postinst but not to be installed
On Fri, Dec 03, 2004 at 06:40:55PM +0100, Philipp Meier wrote:
> On Fri, Dec 03, 2004 at 11:11:58AM -0500, Justin Pryzby wrote:
> > The problem is, that if you have postinst delete the files, they are
> > still registered as belonging to the package. Which is bad, because
> > they wouldn't exist. Donno if there's a way of unregistering files
> > (other than parsing /var/lib/dpkg/info/$pkg.list).
> >
> > The only way to use a file which is not "included in the .deb"
> > (according to dpkg -L) is to create the file. In this case, by
> > ungzipping them from their compressed form in /usr/share/$pkg/. So
> > you still must provide the files "in the .deb". Including them via
> > ./debian/$pkg/tmp/ is bad, because pacakges shouldn't own files in
> > /tmp. Okay, so there's one exception:
>
> Can't the file be included in uuencoded form in the postinst script and
> be extracted by postinst to a temporary location?
Yes, but then it will still persist, after post-installation, as
/var/lib/dpkg/info/$pkg.postinst. It will just be more obfuscated
than /usr/share/$pkg/.
Justin
Reply to: