From owner-freebsd-ports@FreeBSD.ORG Thu Nov 20 13:05:32 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 38EDA147; Thu, 20 Nov 2014 13:05:32 +0000 (UTC) Received: from spectrum.skysmurf.nl (spectrum.skysmurf.nl [82.95.125.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A075F6C2; Thu, 20 Nov 2014 13:05:31 +0000 (UTC) Received: from spectrum.skysmurf.nl (spectrum.skysmurf.nl [82.95.125.145]) by spectrum.skysmurf.nl (8.14.9/8.14.9) with SMTP id sAKD5LRU063203; Thu, 20 Nov 2014 14:05:22 +0100 (CET) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Thu, 20 Nov 2014 14:05:21 +0100 Date: Thu, 20 Nov 2014 14:05:21 +0100 From: "A.J. 'Fonz' van Werven" To: "Russell L. Carter" Subject: Re: latex-texmf required-by Message-ID: <20141120130521.GA46782@spectrum.skysmurf.nl> References: <546D60FC.1060102@pinyon.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mYCpIKhGyMATD0i+" Content-Disposition: inline In-Reply-To: <546D60FC.1060102@pinyon.org> X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-tex@freebsd.org, freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Nov 2014 13:05:32 -0000 --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Russell L. Carter wrote: > I do not love the 2+ hours it takes to build the text/latex-texmf > port. I use pkg(8) to maintain a cluster of machines, and I've > checked the major culprits and I don't see how the latex-texmf > dependency occurs. (I don't specify it explicitly.) [snip] > What is the definitive way to figure out how this dependency has got > itself insinuated into my installed ports? There is no ports category "text". Nor is there a port called latex-texmf. You probably mean print/texlive-texmf. On my system, a quick $ pkg info -r texlive-texmf suggests that print/texlive-texmf is a dependency of print/texlive-full (and by extension of several other TeX ports). However, a quick $ make -C /usr/ports/print/texlive-base all-depends-list|grep texmf suggests that print/texlive-base doesn't pull print/texlive-texmf in. So maybe texlive-base instead of texlive-full is for you. HTH, AvW --=20 Imbibo, ergo sum. --mYCpIKhGyMATD0i+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUbecRAAoJEAfP7gJTaCe88JMP/iBzeU262nfnar10N5o4RsEJ t+sVbYuNAbiJU+D+LtddTudVgsLfuOLChfvzJTGIOWaaOSOMFPcNyyU6P87VO43a REqXfzfmkEFn59fLm606u2l9LSBVWeCKuoH79a1CU0jLjtg1IzeUKUkayUwIEUye QLd+SfF1RYL7hApp4oN993nlChbK7q6PfjKYkTq96j+Xc5h7Umn/HYipsYAaNpIv fprWQ5198XfDcNk+VsHuJooab8uhBHOmj3vZ+s1t28oE0bB9u9pwQAcBfqxyzxTL kwA/gfLuO+NOqeW5UJGNo9f+EJT5509lX98SoDtygNnMDC+CXBb/ehsEZStRcDTd ob3TYVIMj2uyVU8opHV4TX+lTL+4/02NO6LUvTlfGWGFASAR6PeruywPQYTE4HTz /EFh0TWuOiVSMV7+CgCI6vAvzBthysY6n7xkrmskSgD3lDuv2HIWM66Iefq4ASN9 QE4Gnsg+VtFnorvL8E6yQgdC38pI5gTsPKX11Mumq0ddeLLL3yhCQDz/yGAR/oY1 4pljiS3emLZkMx2S9MX+a+tCC0qB3x7vekjZ1WAgIHsVVoZlWTPvCpXu11p0H+pr +mRPiU/uxuMOOogrvk2LXy/yHcpUhcV1eQIoi+k5YGvsnBSubu5prum9Ad3NwivZ alwJAwhCMrJbeSZUZpjb =7G4U -----END PGP SIGNATURE----- --mYCpIKhGyMATD0i+--