Re: xterm-color
> But shouldn't xbase then replace and conflict with xterm-color? Yes, it probably should have done that a long time ago. Go ahead and file a bug report so I remember to get that in. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
New package notices via bug tracking system.
I'm moving this over to debian-devel. Hope that's OK. Joey Hess <[EMAIL PROTECTED]> writes: > The real reason I'm replying to this: I wonder what the other developers > think about bug reports that just say a new version is available (as opposed > to, a new version is available, and fixes this nasty bug). I ask because I > was planning on submitting about 50 bug reports on packages where a newer > version is available. I volenteered some time ago on the debian-qa list to > do this, and I have scripts that look at the LSM files on sunsite, and > automatically give me a list of out of date debian packages. > > If people don't like bug reports for this, I can just post the list to > debian-devel. What do people think? I think it's a good idea. I don't always notice when a new version of one of my packages is released, and the bug system makes a nice reminder once I've been notified. -- Rob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: problems with xnest
hmm. xnest should work fine with xfs (I'd used it that way under 3.1.2, when I was developing the gzipped font stuff) but note that the very end of the man page has some warnings about how xnest actually *fakes* all of it's font handling. (Rather than repeat it here, look near the end of man Xnest, under "xnest as a server", for the gruesome details.) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: New package notices via bug tracking system.
> Joey Hess <[EMAIL PROTECTED]> writes: > > The real reason I'm replying to this: I wonder what the other developers > > think about bug reports that just say a new version is available (as opposed > > to, a new version is available, and fixes this nasty bug). > I think it's a good idea. I don't always notice when a new version of > one of my packages is released, and the bug system makes a nice > reminder once I've been notified. > > -- > Rob Me too. The "bug" system is sort of a mis-nomer, it's also great for feature requests and notifying that a new version is available. People shouldn't interpret the number of bugs against a package as an indication of its quality -- they could all just be requests for enhancements. Cheers, - Jim pgp3GWMc2QuE0.pgp Description: PGP signature
Re: dselect installs only main distribution not non-free
[EMAIL PROTECTED] (Bruce Perens) writes: > I think you have to tell dselect where non-free and contrib are so that it > can find their Packages files. It asks about this when you choose an access > method. yes, that's right. I've checked the directories again. Dselect finds the apropritiate Packages files it reports 980 files in base, 20-80 in each section contrib, non-free and local (non-us). But no file is installed from there. I've checked Access CD-ROM and a previosly mounted directory. But after checking the main distribution the installation process stops 8-( Can someone else check this behavior, please? (It's likely that an install through ftp works fine - I can't remember exactly) Any ideas?? Bye Christian -- Christian Leutloff, Aachen, Germany eMail: [EMAIL PROTECTED] http://www.oche.de/~leutloff/ Debian/GNU Linux! Mehr unter http://www.debian.org/ pgpo8SLfFUdoA.pgp Description: PGP signature
Re: How do we encourage bug reports?
Good morning Enrique and others! > > > Perhaps the `bug' package should be priority standard? It does make > > > bug reporting much easier. > > > > Yes, and when it installs itself, from `deity', it should stop with a > > message to be read, (any key to continue) which advertises `bug's > > presence and explains how, why, and when to use it, and invites people > > to do so. > > Wasn't one of our goals to allow an unattended installation? We're far away from that. Many packages are asking questions so that the installation really takes some time, answering all of them, selecting the packages &c. Perhaps you could think over the whole thing and how we could arrange to have an installation without the need to answer questions. Regards Joey -- / Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg / / If you come from outside of Finland, you live in wrong country / / Featuring Debian GNU/Linux motd von irc.funet.fi / -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How do we encourage bug reports?
> Perhaps you could think over the whole thing and how we could arrange > to have an installation without the need to answer questions. The main thing to do is to separate the question asking from the other scripts. SVR4's package system does this by having a request script for each package that needs it. This is the only install script that is allowed access to the tty, so you cannot prompt the user in postinst etc. The request scripts are run first, and produce name=value shell assignments on their stdout --- this is saved in a response file so that they can be used in the pre/postrm as well as in the pre/postinst. You can take the response files from an installed system, and skip the question answering phase. Obviously, we could do better than this, by having the request script populate a configuration database, but that is just an implementation detail. If we provide a couple of programs set_conf_val and get_conf_val for the scripts to use, then the implementation won't affect the scripts anyway. The problems that need to be solved are: unpacking all the request scripts early enough to run them all before the first pre-inst; and making the request scripts able to diagnose what questions to ask, when many other packages may not be installed yet. Cheers, Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: New libc5 (5.4.33-2) for unstable - READ THIS BEFORE INSTALLING IT
Update on the packages I checked: ssh does _not_ use the libc functions when compiled with libc5. So ssh will corrupt the utmp file if used with hamm. Helmut -- Helmut Geyer[EMAIL PROTECTED] public PGP key available : finger [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
libc6
Hi, I'm working on the xdaliclock package, and I will take it to libc6. I have merely recompiled it, and all has worked fine, except perhaps some warning (perhaps present with libc5: I have not installed alt-libc5 as yet). This is suspect to me, because my X libs are compiled with libc5, and in this list I've read that ncurses (simpler than X libs) give problems with libc6 in compile time. Perhaps I'dont have understand well the problem: can you explain it to me? ciao Francesco Tapparo [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
RE: libc6
I've recompiled some programs that use X with libc6 and they run like a charm. A few minutes ago I recompiled the latest procps suite for testing purposes. For instance xload: gauss:meskes 113) ldd /usr/X11R6/bin/xload libXaw.so.6 => /usr/X11R6/lib/Xaw95/libXaw.so.6 (0x4001) libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x40065000) libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x40077000) libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x400b9000) libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x400c2000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x400d7000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x400e2000) libproc.so.1.12 => /lib/libproc.so.1.12 (0x40182000) libc.so.6 => /lib/libc.so.6 (0x40193000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) gauss:meskes 114) Michael -- Dr. Michael Meskes, Projekt-Manager| topsystem Systemhaus GmbH [EMAIL PROTECTED]| Europark A2, Adenauerstr. 20 [EMAIL PROTECTED] | 52146 Wuerselen Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44 Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10 >-Original Message- >From: Francesco Tapparo [SMTP:[EMAIL PROTECTED] >Sent: Wednesday, June 11, 1997 1:29 PM >To:debian-devel@lists.debian.org >Cc:Die Adresse des Empfängers ist unbekannt. >Subject: libc6 > >Hi, >I'm working on the xdaliclock package, and I will take it to libc6. I have >merely recompiled it, and all has worked fine, except perhaps some warning >(perhaps present with libc5: I have not installed alt-libc5 as yet). This is >suspect to me, because my X libs are compiled with libc5, and in this list >I've read that ncurses (simpler than X libs) give problems with libc6 >in compile time. Perhaps I'dont have understand well the problem: can you >explain it to me? > >ciao >Francesco Tapparo >[EMAIL PROTECTED] > > >-- >TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to >[EMAIL PROTECTED] . >Trouble? e-mail to [EMAIL PROTECTED] . > -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc6
Francesco Tapparo <[EMAIL PROTECTED]> writes: > I'm working on the xdaliclock package, and I will take it to libc6. I have > merely recompiled it, and all has worked fine, except perhaps some warning > (perhaps present with libc5: I have not installed alt-libc5 as yet). This is > suspect to me, because my X libs are compiled with libc5, and in this list > I've read that ncurses (simpler than X libs) give problems with libc6 > in compile time. Perhaps I'dont have understand well the problem: can you > explain it to me? Maybe I misunderstand, but it sounds like you're trying to compile a binary against libc5 versions of some libraries and libc6 versions of others. That will never work. Guy -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc6
On Jun 11, Guy Maor wrote > > I'm working on the xdaliclock package, and I will take it to libc6. I > > have merely recompiled it, and all has worked fine, except perhaps some > > warning (perhaps present with libc5: I have not installed alt-libc5 as > > yet). This is suspect to me, because my X libs are compiled with libc5, > > and in this list I've read that ncurses (simpler than X libs) give > > problems with libc6 in compile time. Perhaps I'dont have understand well > > the problem: can you explain it to me? > > Maybe I misunderstand, but it sounds like you're trying to compile a > binary against libc5 versions of some libraries and libc6 versions of > others. That will never work. No. The surprising thing is that it _does_ work. (e.g. take the DDD source in a libc6 environment, with libc6 libg++272, libc5 ncurses, X etc. It compiles and works). The problem is that there could be subtle problems from the interaction between libc5 and libc6 libraries, which may be very difficult to track. This means that maintainers who work in a libc6 environment must check very carefully that all the libraries they link against are really for use with libc6. Ray -- Cyberspace, a final frontier. These are the voyages of my messages, on a lightspeed mission to explore strange new systems and to boldly go where no data has gone before. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc6
> On Jun 11, Guy Maor wrote > > > I'm working on the xdaliclock package, and I will take it to libc6. I > > > have merely recompiled it, and all has worked fine, except perhaps some > > > warning (perhaps present with libc5: I have not installed alt-libc5 as > > > yet). This is suspect to me, because my X libs are compiled with libc5, > > > and in this list I've read that ncurses (simpler than X libs) give > > > problems with libc6 in compile time. Perhaps I'dont have understand well > > > the problem: can you explain it to me? > > > > Maybe I misunderstand, but it sounds like you're trying to compile a > > binary against libc5 versions of some libraries and libc6 versions of > > others. That will never work. > > No. The surprising thing is that it _does_ work. (e.g. take the DDD source > in a libc6 environment, with libc6 libg++272, libc5 ncurses, X etc. It > compiles and works). The problem is that there could be subtle problems from > the interaction between libc5 and libc6 libraries, which may be very > difficult to track. This means that maintainers who work in a libc6 > environment must check very carefully that all the libraries they link > against are really for use with libc6. > H.J. Lu and the XFree86 team did a lot of work to make this work. whether it works perfectly, I don't know but as X uses its own datatypes for most things one of the main problems of incompatibility between libc5 and libc6 is not present. Helmut -- Helmut Geyer[EMAIL PROTECTED] public PGP key available : finger [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc6
[EMAIL PROTECTED] (J.H.M.Dassen) writes: > No. The surprising thing is that it _does_ work. (e.g. take the DDD source > in a libc6 environment, with libc6 libg++272, libc5 ncurses, X etc. It > compiles and works). Yes, Helmut just told me the same - that H.J. Lu and XFree86 team worked together to allow this. I'm still suspicous of other libraries. If the libc5 library uses ANY libc5 function which has changed calling convention or any struct which has changed, it won't work. Guy -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc6
When will we get libc6 X packages ? Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc6
On Jun 11, Michael Meskes wrote > I've recompiled some programs that use X with libc6 and they run like a > charm. A few minutes ago I recompiled the latest procps suite for > testing purposes. For instance xload: > > gauss:meskes 113) ldd /usr/X11R6/bin/xload > libXaw.so.6 => /usr/X11R6/lib/Xaw95/libXaw.so.6 (0x4001) > libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x40065000) > libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x40077000) > libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x400b9000) > libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x400c2000) > libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x400d7000) > libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x400e2000) > libproc.so.1.12 => /lib/libproc.so.1.12 (0x40182000) > libc.so.6 => /lib/libc.so.6 (0x40193000) > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) > gauss:meskes 114) > > Michael > > -- > Dr. Michael Meskes, Projekt-Manager| topsystem Systemhaus GmbH > [EMAIL PROTECTED]| Europark A2, Adenauerstr. 20 > [EMAIL PROTECTED] | 52146 Wuerselen > Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44 > Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10 > > >-Original Message- > >From:Francesco Tapparo [SMTP:[EMAIL PROTECTED] > >Sent:Wednesday, June 11, 1997 1:29 PM > >To: debian-devel@lists.debian.org > >Cc: Die Adresse des Empfängers ist unbekannt. > >Subject: libc6 > > > >Hi, > >I'm working on the xdaliclock package, and I will take it to libc6. I have > >merely recompiled it, and all has worked fine, except perhaps some warning > >(perhaps present with libc5: I have not installed alt-libc5 as yet). This is > >suspect to me, because my X libs are compiled with libc5, and in this list > >I've read that ncurses (simpler than X libs) give problems with libc6 > >in compile time. Perhaps I'dont have understand well the problem: can you > >explain it to me? there is a risk that at runtime xdaliclock will broke sometime? If so, the better upload is to unstable or to project/experimental? ciao Francesco Tapparo [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: dselect installs only main distribution not non-free
Christian Leutloff <[EMAIL PROTECTED]> writes:
> --pgp-sign-Multipart_Tue_Jun_10_23:52:51_1997-1
> Content-Type: text/plain; charset=US-ASCII
>
> [EMAIL PROTECTED] (Bruce Perens) writes:
>
> > I think you have to tell dselect where non-free and contrib are so that it
> > can find their Packages files. It asks about this when you choose an access
> > method.
>
> yes, that's right. I've checked the directories again. Dselect finds
> the apropritiate Packages files it reports 980 files in base, 20-80 in
> each section contrib, non-free and local (non-us). But no file is
> installed from there.
>
> I've checked Access CD-ROM and a previosly mounted directory. But
> after checking the main distribution the installation process stops
> 8-(
>
> Can someone else check this behavior, please?
>
> (It's likely that an install through ftp works fine - I can't remember
> exactly)
>
> Any ideas??
>
> Bye
> Christian
>
--- install.origThu Dec 5 07:37:33 1996
+++ install Wed Apr 16 01:47:54 1997
@@ -139,6 +139,7 @@
print "\nProcessing Package files...\n";
my $dist;
foreach $dist (@dists) {
+$dist =~ tr/\//_/;
my $fn = "Packages.$dist";
if (-f $fn) {
print " $dist...\n";
The patch is for /usr/lib/dpkg/methods/ftp and works if I use
following line while updating:
stable hamm/contrib hamm/non-free unstable
Patch is courtesy Tomislav Vujec <[EMAIL PROTECTED]>.
I didn't bother to patch other access methods since I use only ftp
method, but it shouldn't be so hard.
--
Posted by Zlatko Calusic E-mail: <[EMAIL PROTECTED]>
-
Famous last words - Jesus Christ: Father, beam me up.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: Bug#10473: gs-aladdin: Aladdin Ghostscript 5.0 released 1997-06-06
Mark Baker: > > In article <[EMAIL PROTECTED]>, > Joey Hess <[EMAIL PROTECTED]> writes: > > > version is available. I volenteered some time ago on the debian-qa list to > > do this, and I have scripts that look at the LSM files on sunsite, and > > automatically give me a list of out of date debian packages. > > Only do that for linux specific things where sunsite is the canonical site. > Otherwise why wait for someone to upload it to sunsite? I can easily look on sunsite and automatically figure out what versions of stuff is available. There's no easy way for me to check around on all the ftp sites that are the main distribution points for different packages. -- see shy jo -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc6
> When will we get libc6 X packages ? probably in the next week or two (I'll try to push out a 3.3-2 with the dependency problems and XF86Setup problem fixed this weekend, and then convert my stock-1.3 build machine into a mixed-mode machine and work forward from there...) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Configuration (was: Re: How do we encourage bug reports?)
[EMAIL PROTECTED] (Philip Hands) wrote on 11.06.97 in <[EMAIL PROTECTED]>: > The problems that need to be solved are: > unpacking all the request scripts early enough to run them all before the > first pre-inst; > and making the request scripts able to diagnose what questions to ask, > when many other packages may not be installed yet. It should probably work like this: * Locate all packages to be installed (main, non-free, and so on) * From each package, extract the configuration script [1] * Run the configuration scripts [2] * Unpack all the packages * Configure all the packages [1] It would be nice to have a special (very simple) configuration-getting script language for this. This allows us to do intelligent stuff with those files, such as ... [2] ... include the possibilities to request that configuration info from: a. Existing configuration from an older version b. A prepared configuration database of some sort c. A dialog-like interface d. A nice X interface e. a braille-optimized line interface f. [fill in the blanks] For some ideas, look at the kernel configuration, which already does a-e (well, ok, e is not really optimized for braille, but it's probably good enough). The actual configuration in there looks like this - not quite what I envision, but getting there: --- snip --- # # Network configuration # mainmenu_option next_comment comment 'Networking options' bool 'Network firewalls' CONFIG_FIREWALL bool 'Network aliasing' CONFIG_NET_ALIAS bool 'TCP/IP networking' CONFIG_INET if [ "$CONFIG_INET" = "y" ]; then source net/ipv4/Config.in fi comment ' ' tristate 'The IPX protocol' CONFIG_IPX if [ "$CONFIG_IPX" != "n" ]; then bool 'Full internal IPX network' CONFIG_IPX_INTERN fi tristate 'Appletalk DDP' CONFIG_ATALK bool 'Amateur Radio AX.25 Level 2' CONFIG_AX25 if [ "$CONFIG_AX25" = "y" ]; then bool 'AX.25 over Ethernet' CONFIG_BPQETHER bool 'Amateur Radio NET/ROM' CONFIG_NETROM fi if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then bool 'Bridging (EXPERIMENTAL)' CONFIG_BRIDGE fi bool 'Kernel/User network link driver' CONFIG_NETLINK if [ "$CONFIG_NETLINK" = "y" ]; then bool 'Routing messages' CONFIG_RTNETLINK fi endmenu --- snip --- MfG Kai -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Bug#10496: svgatextmode: missing getVGAreg, 600 permissions for samples
On Jun 11, Ricardas Cepas wrote > Package: svgatextmode > Version: 1.5-1 > > get/setVGAreg is missing, They are missing because they are described by the author as "hacker" programs, not necessary for the functioning of the svgatextmode itself. The comment in the source implies that you must be familiar with the source in order to use the utilities. One option is to make a svgatextmode-utils package and include these utilities + utilities from contrib directory in the source that are currently not included in svgatextmode package. However, even in that case, the binaries would be distributed without any documentation (maybe I should put the source somewhere in /usr/doc/svgatextmode-utils ? ). You are the first person to ask me about these, so I need some more feedback before I decide to make the svgatextmode-utils package. BTW, here is the comment I was referring to: /*** *** get/set VGAreg, a simple VGA register hacking program *** *** WARNING: since different SVGA cards use different extra address ranges in any *** of the register sets, no checking is done to make sure you don't attempt to change *** a non-existing register! *** *** This is just a hacking tool! Use at your own risk. It was NOT intended to be *** idiot proof! If you don't understand all this, then don't bother trying to use it. *** ***/ >some files in samples/consoletools are readable > only by the root. > This has already been reported, will fix in the next release coming up soon. Thanks. -- Proudly running Debian Linux! Linux vs. Windows is a no-Win situation Igor Grobman [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Configuration (was: Re: How do we encourage bug reports?)
On 11 Jun 1997, Kai Henningsen wrote: > [EMAIL PROTECTED] (Philip Hands) wrote on 11.06.97 in <[EMAIL PROTECTED]>: > > > The problems that need to be solved are: > > unpacking all the request scripts early enough to run them all before the > > first pre-inst; > > and making the request scripts able to diagnose what questions to ask, > > when many other packages may not be installed yet. > > It should probably work like this: > > * Locate all packages to be installed (main, non-free, and so on) > > * From each package, extract the configuration script [1] > > * Run the configuration scripts [2] > > * Unpack all the packages > > * Configure all the packages > > [1] It would be nice to have a special (very simple) configuration-getting > script language for this. This allows us to do intelligent stuff with > those files, such as ... > > [2] ... include the possibilities to request that configuration info from: >a. Existing configuration from an older version >b. A prepared configuration database of some sort >c. A dialog-like interface >d. A nice X interface >e. a braille-optimized line interface >f. [fill in the blanks] > > For some ideas, look at the kernel configuration, which already does a-e > (well, ok, e is not really optimized for braille, but it's probably good > enough). > > The actual configuration in there looks like this - not quite what I > envision, but getting there: > > --- snip --- I've done this for the configuration script for the package WN. I'm only support the text user interface but hope to move to nice X interface. It would be nice if Debian could standardize on a configuration approach. I think the kernel configuration approach has some merits but any standard would be better than none. -- Jean Pierre -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
New version of dtxtdb (0.15)
pgpGAtHFNd8a1.pgp Description: PGP message
New version of dtxtdb (0.15)
pgp5giZfsgbKh.pgp Description: PGP message
