Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3CAB9457.7050700@ece.gatech.edu> Date: Wed, 03 Apr 2002 18:46:31 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Jan Nieuwenhuizen CC: cygwin-apps AT cygwin DOT com Subject: Re: move texmf-* out of test? References: <3CAB28BA DOT 5090600 AT ece DOT gatech DOT edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Jan Nieuwenhuizen wrote: > Charles Wilson writes: > > >>>As tetex-beta-20001218-4 (now in curr) and texmf-*-20000804-2 seem to >>>work well together, can we remove the test marker from texmf? >>> >>You are the maintainer; it is your decision. >> >>I don't know of any hard rule about "three weeks" -- whatever you, as >>the maintainer, think is appropriate for your packages, is good. >> > > Indeed, I reread setup.html; must have dreamt it up. But how do I go > about moving texmf-* to curr? Would this asking here be enough? Right now, yes -- it requires someone with a shell account on sourceware to edit the setup.hint file -- or scp up a new copy of the setup.hint file -- which contains the necessary changes. > No big problems have shown up, it seems a waste to release a new > version (-3) of such a large package (~30mb binaries, 30mb sources) > without major changes. Sounds like you have a reasonable basis for your decision. :-) Do you want me to fixup texmf*/setup.hint? --Chuck