DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:subject:to:references
	:content-type; q=dns; s=default; b=wdl70TAD03MOclLvF1pdPyunEyKyD
	klU/lXd7U3wYEIyRn2B0zAEMK/ah+NKlA9Qrct+2ef3uS1jQ3ghbwln4zBVptqCo
	iSa31PMBB4S+IcLXE6YGkHH5zAiuOJJVS/i+ud4PzqmjbR0JYh8ZFDIsrZYWGsWC
	EFGNYdWxa6zaUs=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <59e7e340.e9099d0a.ecab9.127a@mx.google.com>
Date: Wed, 18 Oct 2017 16:26:56 -0700 (PDT)
From: Steven Penny <svnpenn@gmail.com>
Subject: Re: Which is it -pc- or -unknown-
To: cygwin@cygwin.com
References: <b0dab24e-629a-4d23-c199-69b60a98b9ad@gmail.com>
Content-Type: text/plain; charset=utf8; format=flowed
User-Agent: Tryst/2.0.1 (github.com/svnpenn/tryst)

On Wed, 18 Oct 2017 08:45:11, Marco Atzeri wrote:
> For a regex pattern you should include both.
> I do not bore which one is built and distributed on my packages.
> 
> E.G. on octave
> 
> /usr/lib/octave/site/oct/i686-pc-cygwin
> /usr/lib/octave/site/oct/x86_64-unknown-cygwin

This is certainly not right. I can understand that we will have some
discrepancies across packages, but having a different vendor in the same package
is unacceptable. It suggests that x86_64-unknown-cygwin and i686-pc-cygwin
differ in more ways that one, which they dont. you let it slide, then people
start asking:

- where is x86_64-pc-cygwin?
- where is i686-unknown-cygwin?

which are both valid questions when a package maintainer does dumb stuff like
this. just realized that for octave package, that is you:

http://cygwin.com/cygwin-pkg-maint

point still stands


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple