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 > > ports/infrastructure/bin > ports/infrastructure/lib > ports/infrastructure/man > > 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 files.
I can only add a yes please, as the current setup is rather confusing. Cheers, Jasper -- Stay Hungry. Stay Foolish.
