I yesterday threw together a RubySection page in the wiki. Now I wanted to hear thoughts if we should add one for every group of ports where we have some implicit policy of how to add ports and if you like the idea at all.
I think of them to state how ports are handled in a certain special-interest section: wether to add them at all or rather use package managers (like gem, eggs, pear, cpan) and point users there, who the interested maintainers for a certain section are, and other topics which would fit here. Another question that tends to come up regularly is the one after dealing with new releases, and how different versions are kept available (executable suffices, or *_select symlink configuration). Another question might be the one after implementions (at least for Ruby case). All these things are not really well suited for main documentation and are quite well kept in wiki. That way they can evolve more easily as well. Parts might also end up being taken into core docs if they establish enough. I would see at least PythonSection, and PerlSection, but there are probably many others which might make sense. Do I overlook some other place where such information is kept? What do you think? Florian -- Florian Ebeling Twitter: febeling [email protected] _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
