Re: RFC: MacPorts Filesystem Hierarchy Standard
I wrote the Filename hierarchy standard for MacPorts. I know there's already porthier(7), but I thought it would be nice to have more specific standard.
So is this meant to replace porthier(7)? Than you should write it up as a patch for the manual page. I don't think we need yet another place for it. Coordinate with markd and simon on this.
No, I meant to replace hier part of the Guide. After this change, porthier change would be followed.
This document defines the standard placement of file and directory installed by MacPorts. This document also intended to replace the existing porthier(7)[1]. Every ports in MacPorts project should follow this standard. Most of this based on hier(7)[2].
The hier part of the guide is meant to provide the source for the porthier.7 man page. It doesn't right now, but we are intending to base all manpages on the guide very shortly, so changing the guide is how to get the man pages changed. Right now the guide has the most up-to-date information because of this pending new way.
I'm not really qualified to comment on the technical merits of your proposal. But I'd be happy to look over what you've written for style and format if it passes approval by our base developers. Mark
The hier part of the guide is meant to provide the source for the porthier.7 man page. It doesn't right now, but we are intending to base all manpages on the guide very shortly, so changing the guide is how to get the man pages changed. Right now the guide has the most up-to-date information because of this pending new way.
It would be nice.
I'm not really qualified to comment on the technical merits of your proposal. But I'd be happy to look over what you've written for style and format if it passes approval by our base developers.
The main advantage I hope this guideline would bring to MacPorts is consistency. No one wants to be in an inconsistent filesystem. Unfortunately MacPorts filesystem is not so good at this point. Let's say I just installed mysql5 and apache2. Where's the configuration files? for mysq5, It's located in ${prefix}/etc/mysql5 by default. for apache2 ${prefix}/apache2/conf/ by default. Where's the log files? mysql5 uses /opt/local/var/db/mysql5 apache2 uses /opt/local/apache2/logs/ Who can say MacPorts' filesystem is consistent? If MacPorts had a strict hier guideline and the project recommended port developer to follow that guide, every conf would be in ${prefix}/etc/${name}/, logs in ${prefix}/var/logs/${name}. It's so clear and easy to remember where to look at when I need it. I believe this would improve MacPorts's usability so much.
js wrote:
Let's say I just installed mysql5 and apache2.
Where's the configuration files? for mysq5, It's located in ${prefix}/etc/mysql5 by default. for apache2 ${prefix}/apache2/conf/ by default.
Where's the log files? mysql5 uses /opt/local/var/db/mysql5 apache2 uses /opt/local/apache2/logs/
That's a special case for apache2 there we came to the conclusion that it should be changed. Rainer
js wrote:
Let's say I just installed mysql5 and apache2.
Where's the configuration files? for mysq5, It's located in ${prefix}/etc/mysql5 by default. for apache2 ${prefix}/apache2/conf/ by default.
Where's the log files? mysql5 uses /opt/local/var/db/mysql5 apache2 uses /opt/local/apache2/logs/
That's a special case for apache2 there we came to the conclusion that it should be changed.
Hmm, taking apache2 for example was not fair. Instead, take php5 for example. it installs the followings. /opt/local/etc/php.ini-dist /opt/local/etc/php.ini-recommended
js wrote:
That's a special case for apache2 there we came to the conclusion that it should be changed.
Hmm, taking apache2 for example was not fair. Instead, take php5 for example. it installs the followings.
/opt/local/etc/php.ini-dist /opt/local/etc/php.ini-recommended
The current system has a problem with configuration files, so it can only install sample/documentation configuration or it would overwrite any settings the user has done... In this case, it needs copying to php.ini to take effect. http://trac.macports.org/projects/macports/ticket/12797 http://trac.macports.org/projects/macports/ticket/2365 Using package managers such as RPM/DEB handles all these, and systems such as Ports uses install/deinstall scripts. --anders
participants (4)
-
Anders F Björklund
-
js
-
markd＠macports.org
-
Rainer Müller