X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=PomH/ld3L9+3fXhYwL/W6c0+9V1jjJyePRgyueQ5CvmKdGla5x5q3
	jU345oCgooOImjfWwdfa4O1IE6Ca5yvCpwFh4+0Xwk9CvmNaOY23fuZbw9p9ZqWi
	FVYsiRvJvw+fgf+nEgMRJpmTEG58CKb2ZT3NJuChn++jFAHYzuj5Sw=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=UNUKKNozwRV3xqg6g5CVyCP1maU=; b=X4z0dB0/Hg15ztmRt/pVSpzaAc8k
	QfwN7vKJNGZbvvXgWusj2PalsB8gECfUDiWVGmEO1ZXqI1YGp3wYUgbvQni5IwMD
	gB/9Y2Ze0v1Tq8gAs8C10fkezF6ZkY5Ui1nc7VpHee3G/hhlBNI52Fhf1OOudt2/
	V1qAsohapB0M8wI=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-02-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1+0vI30EqMnS6/1u7VPh67U
Date:	Wed, 18 Jun 2014 01:35:13 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Website: Package listing not working + cygport query
Message-ID:	<20140618053513.GD4920@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<5395FA98 DOT 5050005 AT tiscali DOT co DOT uk> <20140617143111 DOT GF7138 AT ednor DOT casa DOT cgf DOT cx> <20140617153200 DOT GA6910 AT ednor DOT casa DOT cgf DOT cx> <53A11DDD DOT 6050102 AT cygwin DOT com>
MIME-Version:	1.0
In-Reply-To:	<53A11DDD.6050102@cygwin.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Wed, Jun 18, 2014 at 12:04:29AM -0500, Yaakov Selkowitz wrote:
>On 2014-06-17 10:32, Christopher Faylor wrote:
>> I'm surprised that I haven't seen this before: The name that you used to
>> generate your packages was "David Stacey/None".  My parser wasn't
>> expecting a name with a space and I didn't detect the fact that the
>> parsing failed (#($& just realized that I forgot to fix that).  So it
>> was just outputting a '0' size, one per line.
>>
>> Yaakov, wouldn't it make sense not to just use 0/0 as user/group when
>> generating packages with cygport by forcing --owner=0, --group=0 to the
>> tar command?  I'm not suggesting that this is the right way to fix this
>> particular problem but I don't think it's a good idea to leak people's
>> names and groups out onto the interwebs if we can help it.  It will also
>> make the packages slightly smaller.
>
>That would undermine any legitimate specification of gid/uid.  I would 
>like to see how this is handled in the Linux distros first.

I don't see how the random uid/gids of a user would ever be legitimate.
Some released rpm packages do contain (incorrectly, imo) the uid/gid of
the build system that created them but rpm does have a mechanism for
specifying ownership.  If it was really important that arbitrary
ownership must be assigned for some package then it seems like that
would be another cygport enhancement since there is no easy way for
a package maintainer to force their uid to some other value.

cgf

--
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

- Raw text -