From owner-freebsd-questions@freebsd.org Thu Jul 30 11:07:57 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2DBB9AE920 for ; Thu, 30 Jul 2015 11:07:57 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU004-OMC4S32.hotmail.com (blu004-omc4s32.hotmail.com [65.55.111.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90E181F1F; Thu, 30 Jul 2015 11:07:57 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU436-SMTP199 ([65.55.111.136]) by BLU004-OMC4S32.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Thu, 30 Jul 2015 04:06:50 -0700 X-TMN: [182oEY4F9Wv5Qu17ZdrL63NPhXsCjFaE] X-Originating-Email: [carmel_ny@outlook.com] Message-ID: Date: Thu, 30 Jul 2015 07:06:48 -0400 From: Carmel NY To: FreeBSD FreeBSD , hrs@FreeBSD.org Subject: Re: "tlmgr" on FreeBSD In-Reply-To: <20150730055841.GA59201@biertje.skysmurf.nl> References: <20150730055841.GA59201@biertje.skysmurf.nl> Organization: seibercom NET X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 30 Jul 2015 11:06:50.0036 (UTC) FILETIME=[D54FFF40:01D0CAB7] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jul 2015 11:07:57 -0000 On Thu, 30 Jul 2015 07:58:41 +0200, A.J. "Fonz" van Werven stated: > Carmel NY wrote: > > > Has anyone gotten the "tlmgr" program for maintaining texlive packages, > > etcetera to run on FreeBSD? > > It's in print/texlive-tlmgr. Doesn't it work? No, it doesn't. It is a known problem that has existed for a very long time. Probably since the port was first introduced into FreeBSD. This is an integral part of the port and it should have been fixed. -- Jerry