> > > Regardless of whether packages are using debconf, I have wondered for
> > > *years*
> > > why we didn't at least have the option of logging stdout and stderr from
> > > everything in the install/update process. I think it's a good idea.
> > >
> > > Bdale
> >
> > I have proposed this two yea
On Sun, 23 Sep 2001, Massimo Dal Zotto wrote:
> > > Previously Steve Greenland wrote:
> > > > Stdout and stderr from the maintainer scripts. (This may be obvious, but
> > >> you didn't explicitly list it.)
> > >
> > > No, they should use debconf.
> >
> > Regardless of whether packages are using de
> > Previously Steve Greenland wrote:
> > > Stdout and stderr from the maintainer scripts. (This may be obvious, but
> >> you didn't explicitly list it.)
> >
> > No, they should use debconf.
>
> Regardless of whether packages are using debconf, I have wondered for *years*
> why we didn't at least
[EMAIL PROTECTED] (Wichert Akkerman) writes:
> Previously Steve Greenland wrote:
> > Stdout and stderr from the maintainer scripts. (This may be obvious, but
>> you didn't explicitly list it.)
>
> No, they should use debconf.
Regardless of whether packages are using debconf, I have wondered for *
On Thu, Mar 09, 2000 at 07:14:39PM -0500, Nick Cabatoff wrote:
> So I've decided that I don't feel like waiting any longer for the
> wishlist bug for syslog output from dpkg to be implemented. I've
> written a little shell wrapper that will do this for me, and will make
> it available if anyone li
So I've decided that I don't feel like waiting any longer for the
wishlist bug for syslog output from dpkg to be implemented. I've
written a little shell wrapper that will do this for me, and will make
it available if anyone likes - I may send it here for cricitism
regardless.
However, I realize
6 matches
Mail list logo
