From owner-freebsd-ports  Tue Sep 22 22:53:51 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA10565
          for freebsd-ports-outgoing; Tue, 22 Sep 1998 22:53:51 -0700 (PDT)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10548;
          Tue, 22 Sep 1998 22:53:35 -0700 (PDT)
          (envelope-from asami@vader.cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca3-55.ix.netcom.com [209.109.233.55]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id WAA17846; Tue, 22 Sep 1998 22:53:32 -0700 (PDT)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id WAA11370; Tue, 22 Sep 1998 22:53:29 -0700 (PDT)
Date: Tue, 22 Sep 1998 22:53:29 -0700 (PDT)
Message-Id: <199809230553.WAA11370@silvia.hip.berkeley.edu>
To: jkh@time.cdrom.com
CC: jkh@FreeBSD.ORG, ports@FreeBSD.ORG
In-reply-to: <1140.906523798@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: XFree86 dependency and sysinstall
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

 * I appreciate the desire for this, but the reason I also haven't done
 * this yet stems from the fact that turning an arbitrary tarball into a
 * "package" requires that you contrive a fair amount of data.  Sure, the
 * bulk of the PLIST is just a `tar tf ..' away, but then there's the
 * description information and the dependency list and all the other
 * metainfo which makes a package a lot more than just a tar file.

There won't be any dependency away from XFree86 (just into it), so
that's not a problem.  As for description information, you can just
put "X Window System" in +COMMENT and +DESC, I don't think anyone will 
complain it's too short or anything. :>

 * I'm torn between some shell script which automagically gets run by
 * sysinstall after extracting an X distribution tarball (yay, yet
 * another special-case) or just making the X tarballs packages in the
 * first place, taking what the XFree86 project gives us and then doing
 * an extra conversion step.

Either way is fine.

 * 			      For that matter, we could also build the
 * packages ourselves from the x11/XFree86 port - wouldn't that be just
 * nifty (and a good deal less "astonishing" than the alternatives).  But
 * jmz is the MAINTAINER of that port, you see, so if I push that
 * suggestion really hard you'll only come back and accuse me of trying
 * to get off the hook. :-)

Not really, but that port is not really suited for this -- x11/XFree86
is an interactive port that you answer a bunch of questions to have it
compile exactly what you want, while the stuff we get from XFree86 are
a collection of tarballs from which the user picks what s/he wants.
Unless someone volunteers to break the XFree86 port into the two dozen 
or so mini-ports that builds only part of the tree, they are not
really interchangable.

Satoshi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message