Re: [Cron cd /sourceware/ftp/anonftp/pub/cygwin; /sourceware/infra/bin/cygwin/upset -C -u setup.ini; /usr/local/bin/upx -q -q -q setup.exe || exit 0]

[Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>]

On Wed, Feb 04, 2004 at 09:04:40AM +1100, Robert Collins wrote:
>On Wed, 2004-02-04 at 05:26, Christopher Faylor wrote:
>>----- Forwarded message from Cron Daemon -----
>>From: root (Cron Daemon)
>>Subject: Cron <cgf> cd /sourceware/ftp/anonftp/pub/cygwin; /sourceware/infra/bin/cygwin/upset -C -u setup.ini; /usr/local/bin/upx -q -q -q setup.exe || exit 0
>>Date: 3 Feb 2004 18:20:06 -0000
>>
>>upset: release/xemacs/xemacs-emacs-common/setup.hint:5: unknown key 'conflicts: emacs'
>> 
>>----- End forwarded message -----
>>
>>Please don't invent setup.hint keys...
>
>
>FWIW it's a valid setup.ini key. And has been for quite some time.

Yes, I know.  So you keep saying.  However it is not listed as a valid
keyword in the definitive documentation:

http://cygwin.com/setup.html

  "Lines in setup.hint will consist of one of the following:

  # comment
  @ package
  sdesc: "some text"
  ldesc: "some text"
  skip:
  curr: version
  prev: version
  test: version
  category: name1[ name2...]
  requires: package[ package...]
  external-source: package"

and AFAICT it does nothing in setup.exe.  It is not as if users will be
scanning the setup.hint file looking for conflicts.  So, there is no
reason to provide a false sense of confidence by implementing it in
upset.  Therefore, it should not be used in setup.hint.

cgf