Re: Name clash in prospective package

1996-08-01 Thread Erick Branderhorst
> Not completely alone---I'd prefer prompting about /usr/local. Why? > Because /usr/local on all our machines here (not just debian) is an > nfs-mounted directory, and typically mounted readonly or root-squash > so that I know nothing on the client machines is going to be able to > diddle with it

Re: Quasi-free development tools

1996-08-01 Thread Sven Rudolph
In article <[EMAIL PROTECTED]> Rob Browning <[EMAIL PROTECTED]> writes: > Leland Olds <[EMAIL PROTECTED]> writes: > > > (Do we have anything the links to motif?) mosaic (NCSA Mosaic) does. I only provided a statically linked version yet. When I package a released version of Mosaic I should crea

Re: Overwriting include files

1996-08-01 Thread David Engel
Mr Stuart Lamble writes: > Ok. There is a library available, libelf (currently version 0.5.2), > which is required by a program I was idly toying about with (Eli). > I'm contemplating packaging up Eli, which would imply packaging up > libelf as well. Go ahead and package libelf. It's been on my

Re: color ls (fwd)

1996-08-01 Thread Erick Branderhorst
Answer from Jim Meyering (GNU fileutils mainstream maintainer): > | I copied this to Jim Meyering hoping that he might be able to answer > | your question Michael. > | > | Michael Meskes writes: > | > Erick Branderhorst writes: > | > > This file is in the origianl fileutils source name: dircolors

Re: Name clash in prospective package

1996-08-01 Thread Fernando
I think it would be better to change the name of the Mercury Compiler to something like "mercc". The reasons are: 1) Minimal disturbance to current debian users. They now use mc to launch Midnight Comander. 2) Seniority (?). Midnight Commander took the name first (within Debian

Re: POSIX 1387.2 (package-management)

1996-08-01 Thread Michael Gaertner
On Wed, 31 Jul 1996, Dale Scheetz wrote: > On Tue, 30 Jul 1996, Michael Gaertner wrote: > > > Ever heard of this "standard" for unix-package-management? How should we > > deal with this? > > > How does one get a copy? I can not help you - to get this you have to be a groupmember or you must pay

Re: SLIP not working?

1996-08-01 Thread Andrew Howell
Karl Ferguson writes: > > Hi Everyone... > > I've compiled SLIP into the kernel (2.0.10), however I get this following > message in /var/log/daemon.log: > > Aug 1 10:30:49 orion /sliplogin[319]: attaching slip unit sl0 for karl > Aug 1 10:30:49 orion /sliplogin[319]: /etc/slip.login sl0 9600 3

Re: f2c-960717-0 uploaded to master

1996-08-01 Thread Dirk . Eddelbuettel
Right, I know that lapack-linux website too. Note gcc-2.7.0 and g77-0.5.17 were used, more recent ones are available. g77 got better with 0.5.18, but also slower (according to some very casual measurements I did on one piece of code). Also, Jacob Schiotz doesn't say anything about compiler version

Re: XF86 betas (Re: D68K: The next step...)

1996-08-01 Thread Michael Alan Dorman
In message <[EMAIL PROTECTED]>, Mr Stuart Lamble writes: >annoyed that if I want support for my W32p (revision A), I have to go >to 3.1.2E - and it's not available for Debian. Net result: either I >have proper support for my card, and can't install new X-based packages >(dpkg barfs at the postinst

Re: WWW interface to mailing list archive

1996-08-01 Thread J.H.M.Dassen
> I know we have WWW access to our mailing lists one. But as far as I know, it > is only updated monthly. That is incorrect. > Would someone step forward to take care of that on a > daily basis? It will be... once I've rewritten my scripts (due to my thesis deadline, this will probably in Septem

Re: XF86 betas (Re: D68K: The next step...)

1996-08-01 Thread Erick Branderhorst
> Speaking of X, as a member of the beta team (XFree86), I have access to > the source code for the XF86 betas. Would it be worthwhile setting up > packages for these in the contrib section? In particular, I'm kind of > annoyed that if I want support for my W32p (revision A), I have to go > to 3.1

Re: Perl vs Python vs ....

1996-08-01 Thread Dan Stromberg
Ian Jackson wrote: > > We only have room for one `extra' scripting language, besides the > usual sh, awk, sed, &c, on the base disks. > > Perl is widely known. It can solve most problems. There are problems > for which it is difficult to get it to work, but these don't often > occur at installa

Re: f2c-960717-0 uploaded to master

1996-08-01 Thread salwen
>Could you provide a reference to these benchmarks, and the compiler settings >they used? Or better yet, even run them? I don't really use fortran myself, >but link some of my C++ code with Fortran libraries that other folks have >done. But I could do with a speedup of factor 2 ... see the follo

Re: color ls (fwd)

1996-08-01 Thread Dirk . Eddelbuettel
Thanks for forwarding this note by Jim Meyerding. I like his ignoring of /etc/DIR_COLORS, I always found that filename rather ugly and kept my own file /usr/local/etc/colour-ls.rc for these colour settings. IMHO, two things remain: - the fileutils maintainer should patch dircolors so tha

Re: location of sg.h

1996-08-01 Thread David Engel
Mr Stuart Lamble writes: > As of (at the latest) 2.0.0, /usr/include/scsi should be a symbolic link > to /usr/src/linux/include/scsi. Given that libc5 includes the kernel I'll hopefully get time to fix this next week. David -- David EngelOptical Data Systems, Inc. [EMAIL

Re: /usr/doc/copyright/ -> /usr/doc//copyright ?

1996-08-01 Thread Erick Branderhorst
> It's nice to have all these files in the same directory, but people > are starting to do things like having /usr/doc/foo/REAMDE be a link to > /usr/doc/copyright/foo or vice versa, and splitting the documentation > for a package up across several directories doesn't seem to work very > well. Th

Re: use of /usr/share

1996-08-01 Thread Brian C. White
> Erick Branderhorst writes ("use of /usr/share"): > > Perhaps this is a very sensitive subject but shouldn't architecture > > independent things like man pages, info manuals, tex & latex styles > > and a lot of other things being put under a subdir of /usr/share? > > The FSSTND people haven't rea

lyx_0.10.0-1

1996-08-01 Thread Michael Meskes
-BEGIN PGP SIGNED MESSAGE- Date: 31 Jul 96 09:22 UT Format: 1.6 Distribution: unstable stable Urgency: Low Maintainer: Michael Meskes <[EMAIL PROTECTED]> Source: lyx Version: 0.10.0-1 Binary: lyx Architecture: i386 source Description: lyx: High Level Word Processeor (BETA version) Chan

Re: color ls (fwd)

1996-08-01 Thread Erick Branderhorst
Jim Meyering responded: > | This come to via debian mailing list and is about how to activate > | color support for ls. I think the default should be no color at > | all but I doubt if so much aliases as in the message below are the > | proper way to activate color support. Can't this be done i

Re: Bug#3795: ae should not be essential

1996-08-01 Thread Guy Maor
> Christian Hudon writes ("Re: Bug#3795: ae should not be essential"): > > Isn't it that some of the packages that look at EDITOR fall back to ae if > > there are problems with EDITOR? vipw and vigr do this. They're in passwd which is essential, but won't be as soon as I upload a new version. G

Re: /usr/doc/copyright/ -> /usr/doc//copyright ?

1996-08-01 Thread Guy Maor
On Thu, 1 Aug 1996, Ian Jackson wrote: > Should we move the copyright file (and the examples directory) into > the per-package directory in /usr/doc ? I don't think we should move the copyright file. Most people don't ever need to look at them, so it's simpler if they're out of the way. We shou

Re: New virtual package names.

1996-08-01 Thread Dale Scheetz
Well, it's been a while, so lets add: imap-client and imap-server to the virtual package names list. On another note, is there an editor virtual package? Is there any interest in adding one? It could be valuable to add Provides: editor to ae (and others as well). Thanks, Dwarf

New gopher packages

1996-08-01 Thread Michael Meskes
I took the freedom to make gopher bug free. -BEGIN PGP SIGNED MESSAGE- Date: 01 Aug 96 10:03 UT Format: 1.6 Distribution: unstable Urgency: Low Maintainer: Ted Hajek <[EMAIL PROTECTED]> Source: gopher Version: 2.1.1-3 Binary: gopher-client gopherd Architecture: i386 source Description:

Bug#3985: Wrong parameter type in src/getfd.c

1996-08-01 Thread Frank Neumann
Package: kbd Version: 0.91-3 I wondered why the 'loadkeys' program didn't work as expected on m68k, and then I found a little bug in src/getfd.c: It determines the keyboard type via an ioctl (KDGKBTYPE) which returns a char on the kernel side, but is put into a 'long' variable. This just happens