Re: xfree packages

2002-04-16 Thread Steinar Bang

 Ian Burrell [EMAIL PROTECTED]:

 Harold Hunt wrote:

 Also, I request that you keep the XFree86-xserv package, as that
 will allow us to realize the immediate benefit of being able to
 release the Test-** server or updates to the stable server as small
 downloads that everyone can keep up to date with.

 Good idea. I'm going to call it xfree86-xwin though. I think I'll
 put the startup-scripts.tgz in this package.

An extra bonus with this package would be to create minimized installs
that just talk XDMCP to some display manager, and has no X
applications or fonts by its own.

That's how I used CygWin/XFree86 anyway.





Re: xfree packages

2002-04-16 Thread Christopher Faylor

On Wed, Apr 10, 2002 at 01:22:52PM -0700, Ian Burrell wrote:
Christopher Faylor wrote:

Yes, please post the setup.hint files that you used.


Check out http://www.znark.com/cygwin/. It doesn't include the archive 
files; my web account doesn't have the bandwidth or quota for them. To 
generate the packages, download the *.tgz files from 
cygwin/xfree/binaries/4.2.0

If someone wants to repackage these files into .bz2 format, I'll upload
them to a temporary area on sourceware.

cgf



Re: xfree packages

2002-04-16 Thread Roland Glenn McIntosh

cgf - 
If I understood you correctly you wanted the Xfree gzipped archives turned into 
bzipped archives.  I have done this using the 4.2.0 cygwin binaries provided at 
xfree86.org.  I stuck with the .tar.bz2 convention most cygwin packages seem to use.  
Please note that the Xfnts package seems to have .gz files in it (I'm assuming that's 
gzipped fonts) and didn't compress well.

For the rest of the week they can be accessed at:
ftp://rgm.nu/pub/cygwin-xfree/

File list follows.
-rgm

04/17/2002 03:01AM  8,857,283 Xbin.tar.bz2
04/17/2002 03:01AM  1,259,910 Xdoc.tar.bz2
04/17/2002 03:08AM480,598 Xetc.tar.bz2
04/17/2002 03:10AM 12,191,610 Xf100.tar.bz2
04/17/2002 03:10AM371,828 Xfcyr.tar.bz2
04/17/2002 03:10AM344,796 Xfenc.tar.bz2
04/17/2002 03:12AM 16,276,234 Xfnts.tar.bz2
04/17/2002 03:13AM  1,958,413 Xfscl.tar.bz2
04/17/2002 03:13AM206,528 Xfsrv.tar.bz2
04/17/2002 03:13AM891,043 Xhtml.tar.bz2
04/17/2002 03:13AM 85,524 Xjdoc.tar.bz2
04/17/2002 03:13AM 83,977 Xlib.tar.bz2
04/17/2002 03:13AM559,304 Xman.tar.bz2
04/17/2002 03:13AM  1,122,895 Xnest.tar.bz2
04/17/2002 03:13AM607,955 Xprog.tar.bz2
04/17/2002 03:13AM809,720 Xprt.tar.bz2
04/17/2002 03:14AM  4,429,150 Xps.tar.bz2
04/17/2002 03:14AM  1,246,500 Xvfb.tar.bz2
04/17/2002 03:14AM  1,243,049 Xxserv.tar.bz2



At 10:20 PM 04.16.2002 -0400, you wrote:
On Wed, Apr 10, 2002 at 01:22:52PM -0700, Ian Burrell wrote:
Christopher Faylor wrote:

Yes, please post the setup.hint files that you used.


Check out http://www.znark.com/cygwin/. It doesn't include the archive 
files; my web account doesn't have the bandwidth or quota for them. To 
generate the packages, download the *.tgz files from 
cygwin/xfree/binaries/4.2.0

If someone wants to repackage these files into .bz2 format, I'll upload
them to a temporary area on sourceware.

cgf 






RE: xfree packages

2002-04-16 Thread Harold Hunt

Hang on just a minute... I've been making some changes and will have them
finished shortly.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Roland Glenn McIntosh
 Sent: Tuesday, April 16, 2002 11:24 PM
 To: [EMAIL PROTECTED]
 Subject: Re: xfree packages


 cgf -
 If I understood you correctly you wanted the Xfree gzipped
 archives turned into bzipped archives.  I have done this using
 the 4.2.0 cygwin binaries provided at xfree86.org.  I stuck with
 the .tar.bz2 convention most cygwin packages seem to use.  Please
 note that the Xfnts package seems to have .gz files in it (I'm
 assuming that's gzipped fonts) and didn't compress well.

 For the rest of the week they can be accessed at:
 ftp://rgm.nu/pub/cygwin-xfree/

 File list follows.
 -rgm

 04/17/2002 03:01AM  8,857,283 Xbin.tar.bz2
 04/17/2002 03:01AM  1,259,910 Xdoc.tar.bz2
 04/17/2002 03:08AM480,598 Xetc.tar.bz2
 04/17/2002 03:10AM 12,191,610 Xf100.tar.bz2
 04/17/2002 03:10AM371,828 Xfcyr.tar.bz2
 04/17/2002 03:10AM344,796 Xfenc.tar.bz2
 04/17/2002 03:12AM 16,276,234 Xfnts.tar.bz2
 04/17/2002 03:13AM  1,958,413 Xfscl.tar.bz2
 04/17/2002 03:13AM206,528 Xfsrv.tar.bz2
 04/17/2002 03:13AM891,043 Xhtml.tar.bz2
 04/17/2002 03:13AM 85,524 Xjdoc.tar.bz2
 04/17/2002 03:13AM 83,977 Xlib.tar.bz2
 04/17/2002 03:13AM559,304 Xman.tar.bz2
 04/17/2002 03:13AM  1,122,895 Xnest.tar.bz2
 04/17/2002 03:13AM607,955 Xprog.tar.bz2
 04/17/2002 03:13AM809,720 Xprt.tar.bz2
 04/17/2002 03:14AM  4,429,150 Xps.tar.bz2
 04/17/2002 03:14AM  1,246,500 Xvfb.tar.bz2
 04/17/2002 03:14AM  1,243,049 Xxserv.tar.bz2



 At 10:20 PM 04.16.2002 -0400, you wrote:
 On Wed, Apr 10, 2002 at 01:22:52PM -0700, Ian Burrell wrote:
 Christopher Faylor wrote:
 
 Yes, please post the setup.hint files that you used.
 
 
 Check out http://www.znark.com/cygwin/. It doesn't include the archive
 files; my web account doesn't have the bandwidth or quota for them. To
 generate the packages, download the *.tgz files from
 cygwin/xfree/binaries/4.2.0
 
 If someone wants to repackage these files into .bz2 format, I'll upload
 them to a temporary area on sourceware.
 
 cgf







Re: xfree packages

2002-04-16 Thread Christopher Faylor

On Tue, Apr 16, 2002 at 11:23:37PM -0400, Roland Glenn McIntosh wrote:
If I understood you correctly you wanted the Xfree gzipped archives
turned into bzipped archives.  I have done this using the 4.2.0 cygwin
binaries provided at xfree86.org.  I stuck with the .tar.bz2 convention
most cygwin packages seem to use.  Please note that the Xfnts package
seems to have .gz files in it (I'm assuming that's gzipped fonts) and
didn't compress well.

I don't know if it is that simple.  The files should still conform to
the conventions at the oft mentioned: http://cygwin.com/setup.html .
I haven't verified that is the case for the standard .tgz files, though.

I know that Harold is working on this, but I just thought I'd answer
this question.

Regardless, thank you! for taking the initiative.  That was a quick
response.

cgf



Re: xfree packages

2002-04-16 Thread Ian Burrell

Harold Hunt wrote:
 
 Ooos... upon actually looking at the list of files I realized that you
 converted the standard XFree86 tar-gzip files into tar-bz2 files, which
 isn't really what we are trying to do here.  Chris was asking that the
 XFree86 Cygwin-Setup package files be turned into tar-bz2 files; these
 packages can be used with Cygwin's Setup to install Cygwin/XFree86 and they
 are altogether different than the standard XFree86 tar-gzip files.
 

I have uploaded the .tar.bz2 packages to http://www.znark.com/cygwin/. 
The site is limited in bandwidth so it would be best if someone copied 
them somewhere permanent.

If anyone wants to build their own copies, they can use the build.sh 
scripts in that directory. It basically unpacks the .tgz files, 
repackages them in .tar.bz2 files, and shuffles around some of the files.

  - Ian

-- 
[EMAIL PROTECTED]
http://www.znark.com/




RE: xfree packages

2002-04-16 Thread Roland Glenn McIntosh

thanks guys :)
I figured it seemed a little simplistic of a thing to ask.  no worries.
Sorry 'bout that.

G'luck Harold.  I'm going to free some disk space on my server now.

-rgm 





RE: xfree packages

2002-04-16 Thread Harold Hunt

Charles,

Don't bother... I'm already on it.  The scripts are modified and I'm just
working on packaging it up.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Charles Wilson
 Sent: Tuesday, April 16, 2002 11:41 PM
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: Re: xfree packages


 I can do this -- but what was the outcome of the package name argument?
   Was it xfree-foo-4.2.0-1.tar.bz2 or xfree86-... or XFree86-...?

 I'll need to modify the znark script accordingly.

 --Chuck


 Christopher Faylor wrote:

  On Wed, Apr 10, 2002 at 01:22:52PM -0700, Ian Burrell wrote:
 
 Christopher Faylor wrote:
 
 Yes, please post the setup.hint files that you used.
 
 
 Check out http://www.znark.com/cygwin/. It doesn't include the archive
 files; my web account doesn't have the bandwidth or quota for them. To
 generate the packages, download the *.tgz files from
 cygwin/xfree/binaries/4.2.0
 
 
  If someone wants to repackage these files into .bz2 format, I'll upload
  them to a temporary area on sourceware.
 
  cgf
 






Re: xfree packages

2002-04-16 Thread Charles Wilson

Oh okay -- then I can go home (nothin to see here; nope, NOT using the 
superfast net connection at work for non-work related stuff...nope, not 
me...)

--Chuck


Harold Hunt wrote:

 Charles,
 
 Don't bother... I'm already on it.  The scripts are modified and I'm just
 working on packaging it up.
 
 Harold
 
 
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Charles Wilson
Sent: Tuesday, April 16, 2002 11:41 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: xfree packages


I can do this -- but what was the outcome of the package name argument?
  Was it xfree-foo-4.2.0-1.tar.bz2 or xfree86-... or XFree86-...?

I'll need to modify the znark script accordingly.

--Chuck


Christopher Faylor wrote:


On Wed, Apr 10, 2002 at 01:22:52PM -0700, Ian Burrell wrote:


Christopher Faylor wrote:


Yes, please post the setup.hint files that you used.



Check out http://www.znark.com/cygwin/. It doesn't include the archive
files; my web account doesn't have the bandwidth or quota for them. To
generate the packages, download the *.tgz files from
cygwin/xfree/binaries/4.2.0


If someone wants to repackage these files into .bz2 format, I'll upload
them to a temporary area on sourceware.

cgf



 





RE: xfree packages

2002-04-16 Thread Harold Hunt

I need a sample command line for upset.  I have searched and searched and I
haven't found a single example of how to tell it which setup.hint files to
look at and which setup.ini file to generate.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Harold Hunt
 Sent: Tuesday, April 16, 2002 11:43 PM
 To: Charles Wilson; [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: RE: xfree packages


 Charles,

 Don't bother... I'm already on it.  The scripts are modified and I'm just
 working on packaging it up.

 Harold

  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of Charles Wilson
  Sent: Tuesday, April 16, 2002 11:41 PM
  To: [EMAIL PROTECTED]
  Cc: [EMAIL PROTECTED]
  Subject: Re: xfree packages
 
 
  I can do this -- but what was the outcome of the package name argument?
Was it xfree-foo-4.2.0-1.tar.bz2 or xfree86-... or XFree86-...?
 
  I'll need to modify the znark script accordingly.
 
  --Chuck
 
 
  Christopher Faylor wrote:
 
   On Wed, Apr 10, 2002 at 01:22:52PM -0700, Ian Burrell wrote:
  
  Christopher Faylor wrote:
  
  Yes, please post the setup.hint files that you used.
  
  
  Check out http://www.znark.com/cygwin/. It doesn't include the archive
  files; my web account doesn't have the bandwidth or quota for them. To
  generate the packages, download the *.tgz files from
  cygwin/xfree/binaries/4.2.0
  
  
   If someone wants to repackage these files into .bz2 format,
 I'll upload
   them to a temporary area on sourceware.
  
   cgf
  
 
 





RE: xfree packages

2002-04-16 Thread Harold Hunt

Ian,

Okay, I've gotten the Cygwin/XFree86 packages to install via Cygwin's
setup.exe, but there is a slight problem: the usr/X11R6/bin, etc.
directories are created relative to the location of setup.exe, not in the
root of the Cygwin installation.  Any ideas as to what is causing this?

Harold




Re: xfree packages

2002-04-11 Thread Ian Burrell

Harold Hunt wrote:
 
 That sounds fine.
 
 Can I also request that you use a seperate variable for the server version
 number?  I'd ask that because the server will tend to get updated often
 while most of the other packages will never be updated.
 
 I'm really looking forward to these packages getting finished.
 
 Do you think you've got a handle on creating the symlinks that Xinstall.sh
 creates?
 

Did you notice any symlinks that were missing? The build.sh script is 
supposed to create and package the links that Xinstall.sh makes. I don't 
think Xinstall.sh behaviour is quite right for the xkb files.

I posted the xfree86-xwin package and modified xfree86-base to my web 
site. I have appended the new setup.hint files.

  - Ian

-- 
[EMAIL PROTECTED]
http://www.znark.com/


xfree86-base:

sdesc: Cygwin/XFree86 base
category: XFree86
requires: cygwin ash xfree86-fonts xfree86-xwin
ldesc: Cygwin/XFree86 is a port of the X Window System to Cygwin.

This package contains the programs, libraries, and config files needed
to run an X server and clients. It also include the X clients from the
standard X distribution like xterm and twm. You will need to install
the xfree86-xwin package with the Windows X server. The xfree86-fonts
package is also required. The other packages contain headers,
programs, and documentation for development.


xfree86-xwin:

sdesc: Cygwin/XFree86 Windows X server
category: XFree86
requires: cygwin xfree86-base
ldesc: XWin is the X server for Windows. It can run in two different
modes, full screen or inside Windows window. It has four different
engines to drawing, Shadow GDI, Shadow DirectDraw, and Native GDI.





Re: xfree packages

2002-04-11 Thread Jan Nieuwenhuizen

Christopher Faylor [EMAIL PROTECTED] writes:

 AFAICT, both Red Hat and Debian allow upper/lower case, so there's no
 reason for us to restrict things.

All Debian packages are lower case, of course.  TAB completion is a
silly argument against using mixed case, but I just couldn't imagine
anyone would want mixed case package names, if they had a choice.
Probably a matter of taste, I'll try to get used to it :-)

Jan.

-- 
Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org




Re: xfree packages

2002-04-11 Thread Christopher Faylor

On Wed, Apr 10, 2002 at 05:27:14PM -0400, Charles Wilson wrote:
Ian, Chris wants the setup hint files IN the mailing list archive 
permanently.  Not sitting on an external, subject-to-change website.

I've pasted them here.

These look ok except the version: field is a no-op in setup.hint and
should be removed.

Has anyone looked at the packages themselves?

cgf

--- xfree86-base ---
sdesc: Cygwin/XFree86 base
category: XFree86
requires: cygwin ash xfree86-fonts
ldesc: Cygwin/XFree86 is a port of the X Window System to Cygwin. The
X server runs under Windows and displays X clients running on the
local or other machines. It can run in full screen and single window
modes.

This package contains the programs, libraries, and config files to run
the X server and other X clients. The xfree86-fonts package is also
required. The other packages contain headers, programs, and
documentation for development.


--- xfree86-devel ---
sdesc: Cygwin/XFree86 development files
category: XFree86
requires: xfree86-base
ldesc: This package contains the libraries, headers, and man pages
for compiling X Windows programs.


--- xfree86-doc ---
sdesc: Cygwin/XFree86 text documentation
category: XFree86
ldesc: XFree86 development documentation in text, HTML, and PostScript 
formats.

--- xfree86-fonts ---
sdesc: Cygwin-XFree86 fonts
category: XFree86
requires: xfree86-base
ldesc: This package contains fonts for XFree86. It contains the
100dpi, 75dpi, misc, scaled, and cyrillic sets. This package is
required.


--- xfree86-xfs ---
sdesc: Cygwin/XFree86 font server
category: XFree86
requires: cygwin xfree86-base
version: 4.2.0-1
ldesc: This package contains the font server for XFree86.


--- xfree86-xnest ---
sdesc: Cygwin/XFree86 nested server
category: XFree86
requires: cygwin xfree86-base
version: 4.2.0-1
ldesc: Xnest is an X server that runs as a client for another X
server. It is used for testing X clients and servers.


--- xfree86-xprt ---
sdesc: Cygwin/XFree86 printing server
category: XFree86
requires: cygwin xfree86-base
version: 4.2.0-1
ldesc: Xprt is an X server that prints the display to a PostScript file.


--- xfree86-xvfb ---
sdesc: Cygwin-XFree86 virtual framebuffer server
category: XFree86
requires: cygwin xfree86-base
version: 4.2.0-1
ldesc: Xvfb is an X server that runs without any display using a
virtual framebuffer. This server runs without any display. It is used
for testing X clients and servers.



RE: xfree packages

2002-04-11 Thread Harold Hunt

Ian,

 Good idea. I'm going to call it xfree86-xwin though. I think I'll put
 the startup-scripts.tgz in this package.

That sounds fine.

Can I also request that you use a seperate variable for the server version
number?  I'd ask that because the server will tend to get updated often
while most of the other packages will never be updated.

I'm really looking forward to these packages getting finished.

Do you think you've got a handle on creating the symlinks that Xinstall.sh
creates?

Harold


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Ian Burrell
 Sent: Wednesday, April 10, 2002 5:38 PM
 To: Harold Hunt
 Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Subject: Re: xfree packages


 Harold Hunt wrote:
  Yes, we try to keep things regularized around here, so XFree86
 is the way
  that the package names need to be spelled.
 
  Also, I request that you keep the XFree86-xserv package, as
 that will allow
  us to realize the immediate benefit of being able to release the Test-**
  server or updates to the stable server as small downloads that
 everyone can
  keep up to date with.
 

 Good idea. I'm going to call it xfree86-xwin though. I think I'll put
 the startup-scripts.tgz in this package.

   - Ian

 --
 [EMAIL PROTECTED]
 http://www.znark.com/





Re: xfree packages

2002-04-10 Thread Jan Nieuwenhuizen

Robert Collins [EMAIL PROTECTED] writes:

 Setup is case insensitive to package names. I don't see any technical
 issue either way.

Me neither, I only see a social issue: it's just plain irritating for
people?

   tar xjf releases/mysTABTAB beep ^U
   tar xjf releases/MyTABTAB beep ^U

etc, aargh?  It's ever more annoying when you're using wget, and try
to guess the name.

Well, it's only a minor pain, and maybe it's just me.
   
Jan.
-- 
Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org




RE: xfree packages

2002-04-10 Thread Harold Hunt

Yes, we try to keep things regularized around here, so XFree86 is the way
that the package names need to be spelled.

Also, I request that you keep the XFree86-xserv package, as that will allow
us to realize the immediate benefit of being able to release the Test-**
server or updates to the stable server as small downloads that everyone can
keep up to date with.

Thanks for you great work,

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Faylor
 Sent: Wednesday, April 10, 2002 1:35 AM
 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Subject: Re: xfree packages


 On Tue, Apr 09, 2002 at 09:40:46PM -0700, Ian Burrell wrote:
 I finished making some xfree packages. They are distributed binary
 archives repackaged as cygwin packages. I made a package directory that
 can be used with setup.exe from a local directory and over the network.
 
 I changed my mind about the division of the packages I proposed. I got
 rid of the multiple doc and fonts packages cause I was having trouble
 with the naming and directories. Plus, I assumed the people would want
 to install them together. The packages are now:
 
 xfree-base
 xfree-devel
 xfree-docs
 xfree-fonts
 xfree-xfs
 xfree-xnest
 xfree-xvfb
 xfree-xprt
 
 I don't have a machine that people can easily download the full files
 from. I can post the setup.* files and scripts I used to build
 the packages.

 Yes, please post the setup.hint files that you used.

 I think that these files should be called XFree86-base (or just
 XFree86), etc.  The project is the Cygwin/XFree86 project and I
 think the package names should reflect that.

 cgf




RE: xfree packages

2002-04-10 Thread Harold Hunt

Earnie,

 Let's be real picky:

 XFree86-xserv-major.minor-portrelease.tar.bz2 is what is required for
 the binary release.
 XFree86-xserv-major.minor-portrelease-src.tar.bz2 is what is required
 for the source release.

 I've used xserv only as an example scenario and I'm not picking on it
 specifically.

That's pretty close, but XFree86 specifies three version number, so it would
actually have to be:

XFree86-xserv-major.minor.other-portrelease.tar.bz2

XFree86-xserv-major.minor.other-portrelease-src.tar.bz2

Harold

 -Original Message-
 From: Earnie Boyd [mailto:[EMAIL PROTECTED]]
 Sent: Wednesday, April 10, 2002 8:58 AM
 To: Harold Hunt
 Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Subject: Re: xfree packages


 Let's be real picky:

 XFree86-xserv-major.minor-portrelease.tar.bz2 is what is required for
 the binary release.
 XFree86-xserv-major.minor-portrelease-src.tar.bz2 is what is required
 for the source release.

 I've used xserv only as an example scenario and I'm not picking on it
 specifically.

 Earnie.

 Harold Hunt wrote:
 
  Yes, we try to keep things regularized around here, so XFree86
 is the way
  that the package names need to be spelled.
 
  Also, I request that you keep the XFree86-xserv package, as
 that will allow
  us to realize the immediate benefit of being able to release the Test-**
  server or updates to the stable server as small downloads that
 everyone can
  keep up to date with.
 
  Thanks for you great work,
 
  Harold
 
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Faylor
   Sent: Wednesday, April 10, 2002 1:35 AM
   To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
   Subject: Re: xfree packages
  
  
   On Tue, Apr 09, 2002 at 09:40:46PM -0700, Ian Burrell wrote:
   I finished making some xfree packages. They are distributed binary
   archives repackaged as cygwin packages. I made a package
 directory that
   can be used with setup.exe from a local directory and over
 the network.
   
   I changed my mind about the division of the packages I
 proposed. I got
   rid of the multiple doc and fonts packages cause I was having trouble
   with the naming and directories. Plus, I assumed the people
 would want
   to install them together. The packages are now:
   
   xfree-base
   xfree-devel
   xfree-docs
   xfree-fonts
   xfree-xfs
   xfree-xnest
   xfree-xvfb
   xfree-xprt
   
   I don't have a machine that people can easily download the full files
   from. I can post the setup.* files and scripts I used to build
   the packages.
  
   Yes, please post the setup.hint files that you used.
  
   I think that these files should be called XFree86-base (or just
   XFree86), etc.  The project is the Cygwin/XFree86 project and I
   think the package names should reflect that.
  
   cgf

 _
 Do You Yahoo!?
 Get your free @yahoo.com address at http://mail.yahoo.com





Re: xfree packages

2002-04-10 Thread Ian Burrell

Harold Hunt wrote:
 Yes, we try to keep things regularized around here, so XFree86 is the way
 that the package names need to be spelled.
 
 Also, I request that you keep the XFree86-xserv package, as that will allow
 us to realize the immediate benefit of being able to release the Test-**
 server or updates to the stable server as small downloads that everyone can
 keep up to date with.
 

Good idea. I'm going to call it xfree86-xwin though. I think I'll put 
the startup-scripts.tgz in this package.

  - Ian

-- 
[EMAIL PROTECTED]
http://www.znark.com/




Re: xfree packages

2002-04-10 Thread Christopher Faylor

On Wed, Apr 10, 2002 at 09:47:31AM +0200, Jan Nieuwenhuizen wrote:
Robert Collins [EMAIL PROTECTED] writes:

 Setup is case insensitive to package names. I don't see any technical
 issue either way.

Me neither, I only see a social issue: it's just plain irritating for
people?

   tar xjf releases/mysTABTAB beep ^U
   tar xjf releases/MyTABTAB beep ^U

etc, aargh?  It's ever more annoying when you're using wget, and try
to guess the name.

I thought I'd replied to this but I guess I hadn't.

I really don't think we should use tab completion as a justification for
picking package names.  The package names should reflect what the
authors want to call the package.  If the name of the package is XFree86,
it should be called XFree86.  Ditto, TeX, or any other package.

AFAICT, both Red Hat and Debian allow upper/lower case, so there's no
reason for us to restrict things.

cgf



Re: xfree packages

2002-04-10 Thread Larry Hall (RFK Partners, Inc)

At 08:29 PM 4/10/2002, Christopher Faylor wrote:
On Wed, Apr 10, 2002 at 09:47:31AM +0200, Jan Nieuwenhuizen wrote:
 Robert Collins [EMAIL PROTECTED] writes:
 
  Setup is case insensitive to package names. I don't see any technical
  issue either way.
 
 Me neither, I only see a social issue: it's just plain irritating for
 people?
 
tar xjf releases/mysTABTAB beep ^U
tar xjf releases/MyTABTAB beep ^U
 
 etc, aargh?  It's ever more annoying when you're using wget, and try
 to guess the name.

I thought I'd replied to this but I guess I hadn't.

I really don't think we should use tab completion as a justification for
picking package names.  The package names should reflect what the
authors want to call the package.  If the name of the package is XFree86,
it should be called XFree86.  Ditto, TeX, or any other package.

AFAICT, both Red Hat and Debian allow upper/lower case, so there's no
reason for us to restrict things.


I went so far as to type a response and then trash it, since I thought it
was getting off-topic for this list.  But thinking again, it supports 
Chris's position, even though it has been mentioned many a time
on the Cygwin list.  I'm thinking of the 'completion-ignore-case' option
in bash.  Seems to me that this addresses the concern.  

I'm certainly all for mixed-case names.





Larry Hall  [EMAIL PROTECTED]
RFK Partners, Inc.  http://www.rfk.com
838 Washington Street   (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX




xfree packages

2002-04-09 Thread Ian Burrell

I finished making some xfree packages. They are distributed binary 
archives repackaged as cygwin packages. I made a package directory that 
can be used with setup.exe from a local directory and over the network.

I changed my mind about the division of the packages I proposed. I got 
rid of the multiple doc and fonts packages cause I was having trouble 
with the naming and directories. Plus, I assumed the people would want 
to install them together. The packages are now:

xfree-base
xfree-devel
xfree-docs
xfree-fonts
xfree-xfs
xfree-xnest
xfree-xvfb
xfree-xprt

I don't have a machine that people can easily download the full files 
from. I can post the setup.* files and scripts I used to build the packages.

  - Ian

-- 
[EMAIL PROTECTED]
http://www.znark.com/