Date: Fri, 8 Dec 2000 09:59:47 +0200 From: Johann Visagie <wjv@cityip.co.za> To: ports@freebsd.org Subject: ports/22865, anyone? Message-ID: <20001208095947.F40641@fling.sanbi.ac.za> In-Reply-To: <E13vzyl-000271-00@fling.sanbi.ac.za>; from johann@egenetics.com on Wed, Nov 15, 2000 at 12:39:47PM %2B0200 References: <E13vzyl-000271-00@fling.sanbi.ac.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Any chance that a committer with a few free moments can take a look at this PR sometime? I have a port waiting in the wings that depends on this one... johann@egenetics.com on 2000-11-15 (Wed) at 12:39:47 +0200: > > >Number: 22865 > >Category: ports > >Synopsis: New port: devel/omniORBpy I'm open to suggestions from the Python Port Naming Cabal :-) as to improvements. "py-omniORB"? "py-omniorb"? The port for omniORB itself is devel/omniORB (with capitalisation intact). > >Arrival-Date: Wed Nov 15 02:40:01 PST 2000 As I said in the PR: > - There are a number of things I don't like about this port, and I'd > appreciate any advice on how to make it "better". For one thing, omniORBpy > needs the entire pre-built omniORB source tree in order to build. > Currently I copy the whole omniORB source tree over, and this seems messy. > Secondly, this port is highly dependent on the structure of the > devel/omniORB port. Should the omniORB port maintainer change it > radically, the omniORBpy port will break. This port should actually be > rolled into the omniORB port with a user-selectable switch to build it, but > how would one then construct a dependency specifically on omniORBpy (and > there will be ones - I'm working on such a port at the moment)? Thanks, -- Johann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001208095947.F40641>