Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Aug 2005 19:11:19 +0200
From:      Thierry Thomas <thierry@FreeBSD.org>
To:        Paul Schmehl <pauls@utdallas.edu>
Cc:        ports@freebsd.org, Sam Lawrance <boris@brooknet.com.au>
Subject:   Re: PR machine broken?
Message-ID:  <20050801171119.GA18352@graf.pompo.net>
In-Reply-To: <BA66FB8CA2BB6E772258D7FC@utd59514.utdallas.edu>
References:  <2E1EC4D96E17CB668506B6A5@utd59514.utdallas.edu> <1122910887.789.15.camel@dirk.no.domain> <20050801163712.GA9070@graf.pompo.net> <BA66FB8CA2BB6E772258D7FC@utd59514.utdallas.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Le Lun  1 aoû 05 à 18:44:18 +0200, Paul Schmehl <pauls@utdallas.edu>
 écrivait :
> >By the way, this is really an update, and the RCS tag must be preserved.
> >You should resubmit it as a patch, because it will be committed this
> >way, and we want to keep the history in CVS.
> >
> OK.  Should I resubmit using the PR that was just issued?

Yes, please. If it is important, you can compress + uuencode it.

> >I had a quick look at this port, and noted something strange: it depends
> >on both tcl/tk 83 and 84; is that normal? CATEGORIES are set to tk83...
> >
> I wasn't sure what to do with that.  The port uses tk84 and does not 
> require tk83, but there *is* no category for tk84 (should one be create?), 
> so I left that alone.

Hmm... you're right! I was sure that tcl84 / tk84 exist.
Yet this port depends on itk, which is linked with tk83.

> I wasn't sure that I should do patches, because the new port is radically 
> different from the old port.  If I do patches, I'll also have to add text 
> explaining the changes.  Not quite sure how to proceed......

A summary would be sufficient.

Regards,
-- 
Th. Thomas.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050801171119.GA18352>