RE: info & Setup 1.43 (new version)

RE: info & Setup 1.43 (new version)

[Bernard Dautrevaux]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2261 bytes --]

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingéniérie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux@microprocess.com
		b.dautrevaux@usa.net
-------------------------------------------- 

> -----Original Message-----
> From: Chris Faylor [ mailto:cgf@cygnus.com ]
> Sent: Wednesday, May 03, 2000 2:37 AM
> To: cygwin@sourceware.cygnus.com
> Cc: DJ Delorie
> Subject: Re: info & Setup 1.43 (new version)
> 
> 
> On Wed, May 03, 2000 at 09:50:59AM +1000, David O'Shea wrote:
> >I installed using setup 1.43 from mirror.aarnet.edu.au 
> again, into C:\,
> >and it worked fine.
> >
> >With regards to info, there just doesn't seem to be a "dir" 
> file (the main
> >directory page you get when you just run "info") in the 
> distribution.  I
> >made one this way:
> >
> >cd /usr/info
> >for F in *.info texinfo; do
> >install-info --info-dir=. $F
> >done
> >
> >Got a few errors about the gzip and time info pages, so I added them
> >manually (dir is basically a plain text file).
> >
> >I don't guarantee that this is neccessarily the right thing 
> to do, but it
> >gives you an info directory anyway.  Apologies in advance if I'm
> >misleading people.
> 
> Isn't there a better way to create a dir file than this?  I 
> have created
> dir files that way myself but I thought I'd discovered a different way
> somewhere along the line.

I think that is the best way to create the dir file; in fact, ideally, that
should be done automatically by setup.exe. 

> 
> If we get a correct dir file, we'll add it to the distribution.

IMHO It's not good to ship a dir file, as users are allowed to install only
parts of cygwin (I hope :-)), so a prebuilt dir file will reference
unexisting info files and may be difficult to maintain.

Regards,

		Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingéniérie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux@microprocess.com
		b.dautrevaux@usa.net
-------------------------------------------- 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: info & Setup 1.43 (new version)

[Chris Faylor]

On Wed, May 03, 2000 at 08:39:38PM +0200, Bernard Dautrevaux wrote:
>> If we get a correct dir file, we'll add it to the distribution.
>
>IMHO It's not good to ship a dir file, as users are allowed to install only
>parts of cygwin (I hope :-)), so a prebuilt dir file will reference
>unexisting info files and may be difficult to maintain.

Actually, by default setup.exe installs everything.  If someone chooses not
to install a complete installation and then is surprised when they do
an "info gcc" and find that gcc is not available, I'm not going to be
incredibly sympathetic.

However, if you want to submit a patch to setup.c, I'll certainly consider
it.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: info & Setup & RPM

[David O'Shea]

On Thu, 4 May 2000, Chris Faylor wrote:
> Actually, by default setup.exe installs everything.  If someone chooses not
> to install a complete installation and then is surprised when they do
> an "info gcc" and find that gcc is not available, I'm not going to be
> incredibly sympathetic.
> 
> However, if you want to submit a patch to setup.c, I'll certainly consider
> it.

I checked a few RPMs from Red Hat Linux (now I've learned that there's a
space in Red Hat) and noted that they just have postinstall scripts that
run install-info.  Maybe a similar sort of thing could be done here,
except just by having a special file in the .tar.gz file which setup
executes (and which can do any kind of specialised setup that is required
for that package).  Does anyone know if the FreeBSD or Slackware package
formats (both use .tar.gz, right?) have any sort of feature like this?
Maybe a port of pkg_add or something would be useful, then (I seem to
remember seeing something about that in the archives).

..or maybe we could have a custom version of the Red Hat installer (okay,
sorry, I know I shouldn't make suggestions like that unless I've got the
time to do it myself!).

Regards,
David


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: info & Setup & RPM

[Chris Faylor]

On Fri, May 05, 2000 at 08:34:31AM +1000, David O'Shea wrote:
>On Thu, 4 May 2000, Chris Faylor wrote:
>> Actually, by default setup.exe installs everything.  If someone chooses not
>> to install a complete installation and then is surprised when they do
>> an "info gcc" and find that gcc is not available, I'm not going to be
>> incredibly sympathetic.
>> 
>> However, if you want to submit a patch to setup.c, I'll certainly consider
>> it.
>
>I checked a few RPMs from Red Hat Linux (now I've learned that there's a
>space in Red Hat) and noted that they just have postinstall scripts that
>run install-info.  Maybe a similar sort of thing could be done here,
>except just by having a special file in the .tar.gz file which setup
>executes (and which can do any kind of specialised setup that is required
>for that package).  Does anyone know if the FreeBSD or Slackware package
>formats (both use .tar.gz, right?) have any sort of feature like this?
>Maybe a port of pkg_add or something would be useful, then (I seem to
>remember seeing something about that in the archives).
>
>..or maybe we could have a custom version of the Red Hat installer (okay,
>sorry, I know I shouldn't make suggestions like that unless I've got the
>time to do it myself!).

Especially after quoting a message where I tried to subtly make this very
point...

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com