On Mon Apr 07 06:42:22 2008, doughera wrote: > > Did you mean to call this auto::macports, or is this step intended to > eventually encompass the FreeBSD-style ports collection as well. I don't > know if macports is a derivative of FreeBSD ports or not. I do know that > NetBSD and OpenBSD both also have a "ports" collection, though I think all > the *BSD collections are reasonably similar. > > If macports is indeed similar to FreeBSD ports, then this is good step > forward. If it is not, however, you might want to reserve the name > auto:ports for the FreeBSD-style ports collection.
Although this configuration step will be skipped if the operating system is not Darwin, I wrote it in such a way that it should be easily extendable to the other BSD ports systems. Hence, I felt it was reasonable to name it auto::ports rather than auto::macports. So, I'm not wedded to 'auto::ports'. I'll certainly change it if people think it's confusing or premature. The only reasons why I didn't make this a "pure" ports-oriented step were: (a) the pre-existing code only referred to Macports, not to, say, BSD ports; (b) I don't have a FreeBSD on which to test. Better still, could some of our developers on FreeBSD take a look at the code and see whether -- apart from the Darwin restriction -- it would work there? Thank you very much.
