From owner-freebsd-ports Mon Jun 22 07:41:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10615 for freebsd-ports-outgoing; Mon, 22 Jun 1998 07:41:22 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from rrzs2.rz.uni-regensburg.de (rrzs2.rz.uni-regensburg.de [132.199.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10579 for ; Mon, 22 Jun 1998 07:41:10 -0700 (PDT) (envelope-from hubert.feyrer@rrzc1.rz.uni-regensburg.de) Received: from rrzc1.rz.uni-regensburg.de (rrzc6.rz.uni-regensburg.de [132.199.3.65]) by rrzs2.rz.uni-regensburg.de (8.8.8/8.8.8) with SMTP id QAA25147; Mon, 22 Jun 1998 16:41:06 +0200 (MET DST) Date: Mon, 22 Jun 1998 16:41:19 +0200 (MET DST) From: Hubert Feyrer X-Sender: feh39068@rrzc6 To: Stefan Eggers Cc: ports@FreeBSD.ORG Subject: Re: Size of a port... In-Reply-To: <199806221356.PAA05209@semyam.dinoco.de> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 22 Jun 1998, Stefan Eggers wrote: > Only for pkg_create I had to use "-S" as "-s" was already in use. And > for the "size only" feature option "-z" as in si(z)e. :-( Maybe > someone has a better idea and can explain why it is better. > > For now I made "-S" give the name of the (optional) file which gets > the size estimation and "-z" to indicate it should only do this > estimation and not actually create a package. > > I would have liked "-s" for the size file and "-S" for the size file > w/o actually creating a package. Hum... well, I don't really see the point in that intermediate file, but if you think it's necessary... :-) What mechanism do you use to store this in precopiled packages and to retrieve it? (I.e. what format did you use in the +CONTENTS file) I hope you aren't depending on the ports collection (and thus your size-file) being installed when trying to find out the size of some package in - say - an ftp-install. :} > Lib changes are usually not that severe I think. How much would they > usually add? A few KByte I suppose. > > The compiler and architecture are the part which convinces me that > this is not a good idea to put into the ports w/o propper identifi- > cation of at least the architecture. The compiler we could just > assume to be the system's compiler. Anybody using something else > should know what he/she is doing anyway. Well, I prefer actual values instead of rough estimates. And for the compiler, there might be architectures that use egcs, and others that (still) use gcc here, some of them RISC, others CISC happily intermixed. Moreover, imagine the impact of other package variables like NOPORTSDIR(sp?) employed at pkg create time, which will also result in the pkg size differ. (The reason I try to argue here is to get *BSD not too far apart - at least from the interface's point of view :-) - Hubert -- Hubert Feyrer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message