This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Need a ghostscript maintainer
Cygwin path unixlike and the ability to use GS in scripts are crucial
at least for `teTeX' if one want manipulate figures (for example):
futhermore is hard to say what is crucial or not for an arbitrary user.
As other basic tools, GS is needed to a get a good unixlike environment.
Dmitry Timoshkov wrote:
>
> "Robert Collins" <robert.collins@itdomain.com.au> wrote:
>
> > > > On Thu, Jun 28, 2001 at 10:15:47PM -0400, Christopher Faylor wrote:
> > > > >Anyone interested in being the new ghostscript maintainer?
> > > > >
> > > > >The old one is too busy currently.
> > > > >
> > > > >Send me private email (?!?) if you're interested.
> > > >
> > > > No takers? Isn't anyone even curious about this? I'll have to remove
> > > > ghostscript from the distribution if we can't get a maintainer.
> > >
> > > Since ghostscript is fairly well supported for native win32 builds
> > (binaries
> > > could be found quite easy too) and presumely doesn't use any unix specific
> > > functionality, it could be possible to not provide it with Cygwin at all.
> >
> > In fact it didn't use to be provided. Users asked for it. Check the
> > archives. (Native ghostscript doesn't support cygwin paths for starters &&
> > what about X support).
>
> Well, cygwin path is not the crucial argument for a user working in the win32
> environment, is it? An X support is not so critical either, while we are not
> talking about remote displays.
> --
> Dmitry.
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/