Re: automated PPL

2003-11-15 Thread Daniel Reed
On 2003-11-15T12:00-0500, Christopher Faylor wrote:
) On Fri, Nov 14, 2003 at 07:00:19PM -0500, Daniel Reed wrote:
) >I am going to start testing a new script to pull out package proposals from
) >cygwin-apps messages. I have a couple small requests that hopefully will not
) >be too intrusive.
) Should we make a package submittal web form which guarantees the kind of
) formatting that you need?
)
) Hmm.  I guess if we made a form, you wouldn't have to parse email messages
) at all.

Yeah, I just didn't want to cramp anyone's style [too much]. One of the most
tedious things I have to do when I release a new version of naim is go to
freshmeat, TUCOWS, etc. and navigate to/fill out forms to announce the new
release.

I was actually in the process of writing a template to use in an online form
when I realized how "simple" the structure really was, and decided it would
probably be just as easy to parse the messages as to ask people to fill out
Yet Another Form.

If anyone *would* prefer to have an online form to generate the message to
cygwin-apps (and possibly the message to cygwin-announce once the update has
been accepted), that's certainly something I can look into as well.

-- 
Daniel Reed <[EMAIL PROTECTED]> http://naim-users.org/nmlorg/   http://naim.n.ml.org/
A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools. -- Douglas Adams, Novelist


New package: suite3270-3.2.20-1

2003-11-15 Thread Peter A. Castro
Daniel, et. all,
  This is a re-proposal of a package set for a suite of 3270 emulators.
I've given it much thought and reorganized things based on various
peoples suggestions.

The suite is composed of one base package, suite3270-3.2.20-1, and
several independent binary packages which reference the base package:

suite3270-3.2.20-1
==
http://www.fruitbat.org/Cygwin/suite3270/setup.hint.suite3270
http://www.fruitbat.org/Cygwin/suite3270/suite3270-3.2.20-1.tar.bz2
http://www.fruitbat.org/Cygwin/suite3270/suite3270-3.2.20-1-src.tar.bz2

c3270-3.2.20-1
==
http://www.fruitbat.org/Cygwin/suite3270/setup.hint.c3270
http://www.fruitbat.org/Cygwin/suite3270/c3270-3.2.20-1.tar.bz2

pr3287-3.2.20-1
===
http://www.fruitbat.org/Cygwin/suite3270/setup.hint.pr3287
http://www.fruitbat.org/Cygwin/suite3270/pr3287-3.2.20-1.tar.bz2

s3270-3.2.20-1
==
http://www.fruitbat.org/Cygwin/suite3270/setup.hint.s3270
http://www.fruitbat.org/Cygwin/suite3270/s3270-3.2.20-1.tar.bz2

tcl3270-3.2.20-1

http://www.fruitbat.org/Cygwin/suite3270/setup.hint.tcl3270
http://www.fruitbat.org/Cygwin/suite3270/tcl3270-3.2.20-1.tar.bz2

x3270-3.2.20-1
==
http://www.fruitbat.org/Cygwin/suite3270/setup.hint.x3270
http://www.fruitbat.org/Cygwin/suite3270/x3270-3.2.20-1.tar.bz2


I've decided to not prefix each emulator with the base package name.
This is in keeping with how this suite is distributed in other
distributions.  If people can find them there they can find them here the
same way.  Each emulator is a distinct and separate binary package.  This
means the name space will be scattered, but I feel this is how it should
be.  People looking for 'x3270' will be looking for it under that name,
not under a prefixed name of 'suite3270-x3270'.  Each emulator has a
specific purpose and usage and is only slightly complimentary to each
other.

I'd like to address a problem Corinna encountered while reviewing a
previous incarnation of this suite:

On Sat, 1 Nov 2003, Corinna Vinschen wrote:
> Btw., I tried a test of the binary c3270.exe.  From the man page I
> got the impression, the emulator should be able to connect to any
> telnet server.  I don't have a OS/390 machine handy so I used the
> telnet server on Cygwin to connect to.  But it fails.  It connects
> and it shows a login prompt.  Then the password is requested by login(1),
> the same as running a standard telnet session.  But for some reason
> I'm always getting a "Login incorrect" message.  When connecting with
> a normal telnet client, I can login, so I don't quite understand how
> this is supposed to work.  Any hint?

This appears to be a CR/LF issue on the telnet server side of things.  A
trace shows that on the client side, a Return sends only a CR (the
default key code for a Return).  But, for whatever reason, the telnet
daemon is sending a CR+LF to the login program's input stream, so it sees
"userid^M" instead of "userid", which, obviously won't work.  Same goes
for the password.

It could be a weird interaction having to do with ipc pipes and how
carriage control is done, or perhaps it's one of the telnet protocol
options (eg: crlf) causing carriage control to be translated into CR+LF.
Unfortunately none of the 3270 emulators lets you set any of the normal
telnet options which might help control this behaviour.  This is largely
because most of these options are ignored once a 3270 mode is negotiated.

For what it's worth, I've connected to other unix (Linux, AIX, Solaris)
telnet servers, which apparently do not have this problem.  Only with the
Cygwin telnet daemon does this appear to happen.  A debug session of the
telnet daemon and/or login would be needed to diagnose things further
(something I don't really have the time to do).

If you wish, at the login and password prompts, press Ctrl-J ()
instead of Return and you can successfully login.  However, you can't do
all that much after logging in, unless you happen to have a termcap entry
for 'ibm-3279-4-e' :)

-- 
Peter A. Castro <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
"Cats are just autistic Dogs" -- Dr. Tony Attwood


Re: automated PPL

2003-11-15 Thread Christopher Faylor
On Fri, Nov 14, 2003 at 07:00:19PM -0500, Daniel Reed wrote:
>I am going to start testing a new script to pull out package proposals from
>cygwin-apps messages. I have a couple small requests that hopefully will not
>be too intrusive.
>
>For messages about only one package, you can simply follow the message
>formatting guidelines Christopher Faylor proposed for cygwin-announce in
>September:
>   http://cygwin.com/ml/cygwin-apps/2003-09/msg00355.html
>Or even more simply, whenever you mention the name of your package, include
>its version number.

Should we make a package submittal web form which guarantees the kind of
formatting that you need?

Hmm.  I guess if we made a form, you wouldn't have to parse email messages
at all.

cgf