Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Jasper Lievisse Adriaanse (jasperhumppa.nl)
Date: Thu Aug 19 2010 - 07:02:53 CDT
On Thu, Aug 19, 2010 at 11:55:22AM +0200, Marc Espie wrote:
> I want to tweak the directory structure for ports.
> I'd like to go for a lot of stuff to
> the current setup (build, fetch, install, package) is my mistake, and
> frankly it sucks. Some of the scripts are callable outside of bsd.port.mk,
> and you have to remember the path. There is no standard documentation out
> of the scripts, and there are a few perl modules that could use one
> single place.
> I would keep db, plist, templates. I don't think they're that confusing.
> The only drawback is that we're going to lose cvs history. doesn't seem
> like such a big problem to me. Also, third party may lose "compatibility"
> as scripts move around. That's easy to solve with symlinks, so I don't
> care too much.
> Did I miss anything ?
I think losing cvs history for mk/ would be worst. But since that dir
doesn't move I don't care too much for losing the history of the other
I can only add a yes please, as the current setup is rather confusing.
Stay Hungry. Stay Foolish.