Previously Antti-Juhani Kaijanaho wrote:
> Let's start with a very simple package, xyzzy. The only thing it
> needs to know is whether the system clock is set to UTC or not.
> How to present this to the frontend? Clearly we need to give it a
> named aggregate of pairs (consisting a label and a
Previously Miquel van Smoorenburg wrote:
> Hmm, has noone in this thread mentioned COAS yet? http://www.coas.org/
Actually, I have. COAS has some drawbacks: it's development is seems
very slow, the mailinglist has no messages except for people complaining
about how to compile it, and it needs all
Antti-Juhani Kaijanaho wrote:
> You just have to design the language to be flexible enough. In this
> post I'll sketch one.
> (datum metoo/foo
> (type yesno)
> (query "Do you want me to do foo?")
> (default yes))
> (if (yes? metoo/foo)
> ((datum metoo/foo2
> (type yesno)
..
You've
Previously Jason Gunthorpe wrote:
> What are you trying to achive? Do you want some sort of tool to pre-scan
> all the .debs, configure them then install?
I want a method to configure packages before unpacking them. If that
involves pre-scanning .deb's, so be it. Doing this is a thing we've wante
Previously Jason Gunthorpe wrote:
> I strongly suspect that if we take a carefull look at what the
> configuration scripts are asking we will find this is not a major hurdle
> for MOST things - and a such should not be the central focus of any
> proposal.
The term "not MOST things" has a tendency
[ Manoj, do you want this on debian-policy or debian-devel? The ammount of
crossposting lately is making those lists even harder to read ]
> Secondly, Could this be made available on a web page somewhere?
Yes, please, Developer's Corner and/or DDP's pages seems like good places
to gather
Sorry for quoting out of order, but..
On Mon, Jul 27, 1998 at 07:27:38PM -0400, Raul Miller wrote:
> Or do we want to talk about creating a query system where the package
> pre-registers its queries with dpkg, and dpkg is allowed to obtain the
> answers to these questions before the package is unp
In article <[EMAIL PROTECTED]>,
Antti-Juhani Kaijanaho <[EMAIL PROTECTED]> wrote:
>On Tue, Jul 28, 1998 at 06:53:09PM -0700, Joey Hess wrote:
>> Yes, I understand the distinction. I see the advantages to having a set
>> of questions, rather than a script. But I doubt it will be flexable enough.
>
>
Hi,
This is all very well, but I would like to clarify why this is
important; I think the benefits and procedures should be stated up
fron. Please consider adding this to the porosal as an preface or
motivation section; after all this is mostly your document, with
additions from me (so
On Tue, Jul 28, 1998 at 06:53:09PM -0700, Joey Hess wrote:
> Yes, I understand the distinction. I see the advantages to having a set
> of questions, rather than a script. But I doubt it will be flexable enough.
You just have to design the language to be flexible enough. In this
post I'll sketch o
On Wed, 29 Jul 1998, Wichert Akkerman wrote:
> Previously Jason Gunthorpe wrote:
> > First, you try not to do that in the postinsts. Look at how M$ forms most
> > of it's configuration and you don't see this. A change of what you want to
> > ask and how you phrase it can likely advoid many of the
On Wed, 29 Jul 1998, Wichert Akkerman wrote:
> Previously Jason Gunthorpe wrote:
> > You are missing what he is saying. The current proposal is that we write
> > basically a script to handle the configuration prompting. A script is
> > probably necessary, but I think it probably should be in the
On Wed, Jul 29, 1998 at 01:16:24AM -0700, John Lapeyre wrote:
>
> The best doc I know of is in /usr/doc/doc-base .
>
> hamish>Can you or one of the doc-base developers give me (or point me at)
> hamish>an executive summary of that doc-base does?
I think doc-base will be ready very so
-BEGIN PGP SIGNED MESSAGE-
On 29 Jul 1998 [EMAIL PROTECTED] wrote:
> [...]
> Then we can localize an internationalized package. For many languages
> And everybody agrees that there is no reason to keep in one package
> all localized versions.
I disagree. The FSF also disagrees. All GNU
Previously Jason Gunthorpe wrote:
> First, you try not to do that in the postinsts. Look at how M$ forms most
> of it's configuration and you don't see this. A change of what you want to
> ask and how you phrase it can likely advoid many of these cases.
Look again. Microsoft has gotten very fond o
Hi,
few weeks ago I statred to translate lang_pl.h (from dinstall from
boot-floppies)
into Polish. At the moment I have made resc???.bin and may install my Debian
GNU/Linux 2.0 talking to me in Polish. Unfortunately not all the time.
Why? because not all programs are localized into polish. Some o
Previously Jason Gunthorpe wrote:
> You are missing what he is saying. The current proposal is that we write
> basically a script to handle the configuration prompting. A script is
> probably necessary, but I think it probably should be in the post/pre inst
> not seperate..
preinst/postinst is way
Previously Manoj Srivastava wrote:
> You started it ;-)
Ehm, guilty I guess. My home system also doesn't take that long, even
though is has an 2 year old mainboard an 4 year old harddisks, no
DMA no nothing:
0.030u 0.070s 0:03.27 3.0% 0+0k 0+0io 102pf+0w
> People like to brows
The best doc I know of is in /usr/doc/doc-base .
hamish>Can you or one of the doc-base developers give me (or point me at)
hamish>an executive summary of that doc-base does?
John Lapeyre <[EMAIL PROTECTED]>
Tucson,AZ http://www.physics.arizona.edu/~lapeyre
--
To UNSUBSCRI
On Tue, Jul 28, 1998 at 05:54:31PM -0700, John Lapeyre wrote:
>
> Is there a way to put some teeth into the requirement to use
> doc-base ? I guess I could start by filing a bunch of bugs (my own pkgs.
> included). It looks like it could really improve the dist. It takes
> quite a bit of
Hi,
>>"Joey" == Joey Hess <[EMAIL PROTECTED]> writes:
Joey> Well we already have a directory structure on the ftp site. The
Joey> problem is it's confusing. Is wget in net (makes ftp
Joey> connections) or web (makes www connections)? Is kernel-package
Joey> in admin (helps the admin do somethi
Manoj Srivastava wrote:
> > As I said, we should design for tomorrow. Not to the constrains of
> > yesterdays technology ;-). I think that adding logical structure to
> > the list of packages is desirable.
Joey Hess <[EMAIL PROTECTED]> wrote:
> Well we already have a directory structure on the
Manoj Srivastava wrote:
> People like to browse through directory structures. File
> systems. Web paages. But suddenly present them with a node with
> several thousand brnaches, and you have lost them.
>
> As I said, we should design for tomorrow. Not to the
> constrains of yesterd
Hi,
>>"Wichert" == Wichert Akkerman <[EMAIL PROTECTED]> writes:
Wichert> [1 ]
Wichert> Previously Manoj Srivastava wrote:
>> Actuall, maybe we should reconsider even that. The ast time I
>> updated apt, 2200+ packages were updated. Having them in a flat
>> folder is not likely to help browsi
Hi,
I think we may be making the mistake of rushing too soon to
implemetation details; I think we need to consider ideas and visions
that have come up before, and even if they are not implemented
immediately, I would rather we put in some thought so that we have
leeway to implement thi
Hi,
Since this has come up in the past, and we had lots of nice
suggestions before, I am posting a giant collection of old and new
proposals. I beg that people review all this, and Wichert, please see
if you can boil all of this down to one (or more) proposals.
-=-=-=-=-=-=-=-=-=-=-=-
On Tue, 28 Jul 1998, Joey Hess wrote:
> Yes, I understand the distinction. I see the advantages to having a set
> of questions, rather than a script. But I doubt it will be flexable enough.
> Consider some examples of the questions asked in postinsts now. They often
> go through a tree of possibl
Jason Gunthorpe wrote:
> You are missing what he is saying. The current proposal is that we write
> basically a script to handle the configuration prompting. A script is
> probably necessary, but I think it probably should be in the post/pre inst
> not seperate..
>
> Anyhow, the point is that what
On Tue, 28 Jul 1998, Joey Hess wrote:
> Antti-Juhani Kaijanaho wrote:
> > I like everything about it, except the language. IMO it has the wrong
> > basic assumption, namely that the configuration module controls the
> > frontend like a programmer controls the machine (the language is
> > essenti
On Tue, 28 Jul 1998, Joey Hess wrote:
joey>I wasn't aware doc-base was fully implemented. Is it?
According to the documentation, no. But this much works...
install-docs -s foo
This tells you where the docs for this package are , what form
they are in and if they are reg
John Lapeyre wrote:
> Is there a way to put some teeth into the requirement to use
> doc-base ? I guess I could start by filing a bunch of bugs (my own pkgs.
> included). It looks like it could really improve the dist. It takes
> quite a bit of practice to learn how to hunt down documents.
Is there a way to put some teeth into the requirement to use
doc-base ? I guess I could start by filing a bunch of bugs (my own pkgs.
included). It looks like it could really improve the dist. It takes
quite a bit of practice to learn how to hunt down documents.
This is from my
Antti-Juhani Kaijanaho wrote:
> I like everything about it, except the language. IMO it has the wrong
> basic assumption, namely that the configuration module controls the
> frontend like a programmer controls the machine (the language is
> essentially astripped-down special-purpose BASIC). I wou
Wichert Akkerman wrote:
> Do you have any comments on my idea for that? I'll qoute it here:
>TEXT is currently defined is a method to add explanatory text to the
>questions. Maybe we should add a command oposite to GO, which says
>"start building a new display, of type (error|message|in
http://www.debian.org/Lists-Archives/debian-devel-9805/msg00995.html
John Lapeyre <[EMAIL PROTECTED]>
Tucson,AZ http://www.physics.arizona.edu/~lapeyre
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, Jul 29, 1998 at 12:15:36AM +0200, Wichert Akkerman wrote:
> so we use a simple language where each command is exactly one line. A
> prelimary list of commands is:
I like everything about your proposal
I like everything about it, except the language. IMO it has the wrong
basic assumption,
Previously Joey Hess wrote:
> One other problem I have with the proposal is that it assumes that questions
> will be askedsequentially. But, this means that you won't be able to answer
> a question, go on to the next, and then go back. (Except within a block of
> questions that are all displayed at
Previously Joey Hess wrote:
> I guess I haven't thought the non-interactive frontends through. I was under
> the impression they had to be pre-seeded with data about the questions. If
> they can just return the default to everything (and everything has a sane
> default of course), that handles non-
38 matches
Mail list logo
