Previously Joey Hess wrote:
> Not really. I named it dpkg-reconfigure for a reason. :-)
Have you thought about how you want to integrate it? I've been looking
into that a bit and it's not trivial.
Wichert.
--
==
This co
On Tue, 21 Sep 1999, Hamish Moffatt wrote:
hamish>On Mon, Sep 20, 1999 at 02:57:42PM -0600, Scott Barker wrote:
hamish>> dpkg -i
hamish>> dpkg-reconfigure
hamish>>
hamish>> you could just run:
hamish>>
hamish>> dpkg -i --reconfigure
hamish>>
hamish>> I'm probably thinking too far ahead right
On Tue, Sep 21, 1999 at 11:02:58AM +1000, Hamish Moffatt wrote:
> Why would you install the package (which presumably includes
> configuration) and then immediately reconfigure it?
You upgrade a package, and it gets installed with your previous configuration,
and you want to change that configurat
Aaron Van Couwenberghe wrote:
> The whole purpose of Wichert's spec is to force packages to install with a
> default configuration, and then reconfigure themselves with data from the
> database after installation. Whether questions are (all) asked before or
> after installation is a secondary point
On Tue, Sep 21, 1999 at 11:02:58AM +1000, Hamish Moffatt wrote:
> On Mon, Sep 20, 1999 at 02:57:42PM -0600, Scott Barker wrote:
> > dpkg -i
> > dpkg-reconfigure
> >
> > you could just run:
> >
> > dpkg -i --reconfigure
> >
> > I'm probably thinking too far ahead right now, though...
>
> Why w
On Mon, Sep 20, 1999 at 02:57:42PM -0600, Scott Barker wrote:
> dpkg -i
> dpkg-reconfigure
>
> you could just run:
>
> dpkg -i --reconfigure
>
> I'm probably thinking too far ahead right now, though...
Why would you install the package (which presumably includes
configuration) and then immedi
On Mon, Sep 20, 1999 at 02:12:06PM -0700, Joey Hess wrote:
> Not really. I named it dpkg-reconfigure for a reason. :-)
Excellent! :)
> Oh, that's not the problem. Dpkg-repack should pick up that file fine. What
> it won't pick up is the actual answers you've given to the questions, which
> are st
Scott Barker wrote:
> Excellent. Hopefully if debconf gets folded into the base system, dpkg itself
> will be able to run this directly, rather than it be an extra step for the
> user. For example, instead of running (manually, or through apt):
>
> dpkg -i
> dpkg-reconfigure
>
> you could just r
On Mon, Sep 20, 1999 at 01:23:50PM -0700, Joey Hess wrote:
> It's now possible in two ways. First, there is the dpkg-reconfigure program,
> which you pass a package name, and it lets you see all the questions again.
Excellent. Hopefully if debconf gets folded into the base system, dpkg itself
wil
Scott Barker wrote:
> 2) I think I presented this suggestion backwards. According to debconf's docs,
>a user will be prompted for the answer to a question only if they haven't
>already answered that question, and only new questions will be presented.
>I'm suggesting there be a way for a
Philip Hands wrote:
> Presumably variable names can have more than one / in them ?
Yes.
> If so, it might be worth calling such variables something like:
>
> shared/news/server
>
> to avoid name space pollution, and to emphasise the fact that there is
> not a package called ``news'' (virtual
Joey Hess <[EMAIL PROTECTED]> writes:
> Steve Greenland wrote:
> > I've read (or at least skimmed) the tutorial you posted, and it
> > looks like the various configuration variables are associated with a
> > package via the template "foo/variable". What about variables that are
> > logically share
On Fri, Sep 17, 1999 at 02:45:32PM -0400, Raul Miller wrote:
> FYI, sash_3.3-5 (which has been sitting in Incoming for the last couple
> weeks) no longer prompts at postinst time, as the postinst/prerm scripts
> have been completely redesigned.
do they automatically set up sash as root's shell?
c
> Well Wichert and I have talked about this.
>
> One nice thing about debconf is it separates out nearly all translatable
> text from the postinst and configure script into it's template file. So it
> merely becomes a question of adding translations to that file. The file is
> formatted similarly
Steve Greenland wrote:
> I've read (or at least skimmed) the tutorial you posted, and it
> looks like the various configuration variables are associated with a
> package via the template "foo/variable". What about variables that are
> logically shared between packages, such as the default directory
Michael Sobolev wrote:
> Is i18n going to be supported by debconf? If yes, how?
Well Wichert and I have talked about this.
One nice thing about debconf is it separates out nearly all translatable
text from the postinst and configure script into it's template file. So it
merely becomes a question
On 17-Sep-99, 13:23 (CDT), Joey Hess <[EMAIL PROTECTED]> wrote:
> This is a bit long, so I'll summarize:
>
> Debconf is a tool that packages can use to ask questions when they are
> installed. It allows various frontends, from dialog, to gtk to web pages
> to be used, and it also allows for
[ announce for debconf skipped ]
Is i18n going to be supported by debconf? If yes, how?
Thanks,
--
Mike (who thinks i18n should be considered from the very beginning)
On Sun, Sep 19, 1999 at 01:16:23PM -0400, Branden Robinson wrote:
> On Sun, Sep 19, 1999 at 12:20:39PM +0200, Martin Schulze wrote:
> > Branden Robinson wrote:
> > > Thanks again, Joey. I look forward to migrating XFree86 to debconf (won't
> > > happen for -1, but I'm hoping to tackle FHS-complian
On Sun, Sep 19, 1999 at 12:20:39PM +0200, Martin Schulze wrote:
> Branden Robinson wrote:
> > Thanks again, Joey. I look forward to migrating XFree86 to debconf (won't
> > happen for -1, but I'm hoping to tackle FHS-compliance and this for -2).
>
> Err, can you please wait for this until a) debco
Branden Robinson wrote:
> Thanks again, Joey. I look forward to migrating XFree86 to debconf (won't
> happen for -1, but I'm hoping to tackle FHS-compliance and this for -2).
Err, can you please wait for this until a) debconf has been accepted and
b) there will be proper support for it and c) pro
I've sent this to the debian-devel list because I've tried to add some
clarification to my suggestions, in case they were unclear to others (it seems
they may have been).
Note that none of my suggestions are in any way negative criticisms. debconf
looks incredibly useful as it is, and I just had s
On Sat, Sep 18, 1999 at 12:50:57PM -0600, Scott Barker wrote:
> Not even a dozen messages into this thread, and already the usual user-bashing
> begins.
I wasn't bashing a user, I was bashing people who levelled criticisms of
debconf before it's even been out 24 hours, and more to the point, befor
Scott Barker wrote:
> For your information, I understand just fine. As near as I can tell, debconf
> needs to be run in the post-install scripts, because there is not yet any
> functionality within the packaging system to define a separate config script.
> That extra functionality is what I'm looki
Scott Barker wrote:
> My reading of it was that you use the debconf functions from within the
> post-install script. I'm talking about a completely new functionality for the
> packaging system, where a config script is defined, and is not the
> post-install script. I will check again, in case I mis
On Sat, Sep 18, 1999 at 02:13:26PM -0400, Branden Robinson wrote:
> On Fri, Sep 17, 1999 at 02:11:20PM -0700, Joey Hess wrote:
> > Have you looked at debconf at all? Because..
> >
> > Scott Barker wrote:
>
> Of course not; people are, sadly, always trying to redesign things they
> don't even unde
On Fri, Sep 17, 1999 at 02:11:20PM -0700, Joey Hess wrote:
> Have you looked at debconf at all? Because..
>
> Scott Barker wrote:
> > 1) Separate interactive and non-interactive installation scripts. I suggest
> >that the current debian install scripts should contain *only*
> >non-interati
On Fri, Sep 17, 1999 at 02:11:20PM -0700, Joey Hess wrote:
> Have you looked at debconf at all? Because..
>
> Scott Barker wrote:
Of course not; people are, sadly, always trying to redesign things they
don't even understand.
I, for one, am delighted to see this tool come to light after years of
Daniel Burrows wrote:
> Another question -- I realize the proposed API has been out for a while, but
> is it possible that the TEXT command could be modified to take a priority?
Actually, debconf uses a variation on the prposed API, that makes text just
be a variety of ui element, like a boolean
Another question -- I realize the proposed API has been out for a while, but
is it possible that the TEXT command could be modified to take a priority?
There are probably notifications that the maintainer scripts could display
which some people would be interested in but many would not, and being
Joey Hess wrote:
> 10%? Just a guess. I did a fresh debian install and picked one of the larger
> profiles, and only about 21 packages out of that profile did any prompting.
> (Results in /usr/share/debconf/packages-that-prompt.)
Er, there should be a 'doc' in that path.
--
see shy jo
Raphael Hertzog wrote:
> I did not yet check/test your work but I'm sure that it's great !
> I wonder if you think that debconf is good/mature enough to be used
> for potato.
Well I've been using it for about a month for just a couple of packages. I
will porbably convert my packages to use it once
Le Fri, Sep 17, 1999 at 11:23:36AM -0700, Joey Hess écrivait:
> This is a bit long, so I'll summarize:
>
> Debconf is a tool that packages can use to ask questions when they are
> installed. It allows various frontends, from dialog, to gtk to web pages
> to be used, and it also allows for no
Daniel Burrows wrote:
> I've got a question about this. If you use the --frontend=Base approach, is
> there any way to "mark" which packages were installed in this way?
No. Though I can see adding it.
> I'd
> personally like to be able to do this but also to go back later and fix up
> configur
Have you looked at debconf at all? Because..
Scott Barker wrote:
> 1) Separate interactive and non-interactive installation scripts. I suggest
>that the current debian install scripts should contain *only*
>non-interative functionality, such as running ldconfig, update-rc.d, etc.
>*All
On Fri, Sep 17, 1999 at 11:57:44AM -0700, Joey Hess was heard to say:
> Ben Gertzfield wrote:
> > This is great, Joey!
> >
> > Can you show an example of how to use apt-get to *skip* configuration
> > questions altogether?
>
> Assumming you have debconf installed, edit /etc/apt/apt.conf, make it
I have some suggestions. Does anyone care to comment?
1) Separate interactive and non-interactive installation scripts. I suggest
that the current debian install scripts should contain *only*
non-interative functionality, such as running ldconfig, update-rc.d, etc.
*All* interactive funct
Raul Miller wrote:
> FYI, sash_3.3-5 (which has been sitting in Incoming for the last couple
> weeks) no longer prompts at postinst time, as the postinst/prerm scripts
> have been completely redesigned.
That's great. The one in the apt repository is of course only a sample.
--
see shy jo
Ben Gertzfield wrote:
> This is great, Joey!
>
> Can you show an example of how to use apt-get to *skip* configuration
> questions altogether?
Assumming you have debconf installed, edit /etc/apt/apt.conf, make it look
like this:
// Pre-configure all packages before they are installed.
DPkg::Pre-
On Fri, Sep 17, 1999 at 11:23:36AM -0700, Joey Hess wrote:
> show to people. If you would like to try out debconf, simply add this line
> to /etc/apt/sources.list:
>
> deb http://va.debian.org/~joeyh/ debconf/
>
> There are a few packages in there modified to use debconf. Good examples
>
This is great, Joey!
Can you show an example of how to use apt-get to *skip* configuration
questions altogether?
Ben
--
Brought to you by the letters W and O and the number 14.
"It should be illegal to yell 'Y2K' in a crowded economy."
Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.
This is a bit long, so I'll summarize:
Debconf is a tool that packages can use to ask questions when they are
installed. It allows various frontends, from dialog, to gtk to web pages
to be used, and it also allows for non-interactive package installs, and
allows packages to ask questions a
42 matches
Mail list logo
