Re: [26541] trunk/doc/guide/xml/portfiles/details.xml
Hi Maun Suang! Well, first of all, on behalf of the entire team thanks again for all this love you're devoting to the until now much abandoned guide, I'm sure a large user base will be very pleased to see this work come to fruition! About one of the changes you made here:
- configuration file /etc/ports/ports.conf. Can be + configuration file ${prefix}/etc/ports/macports.conf. Can be
I plan to release MacPorts 1.5 soon now (I've been preparing base for the last days and think it's time to branch already), so I'd love it if we could detail all throughout the entire guide the new installation layout resulting from the work I did on the dp2mp-move branch. You can read about it here: http://trac.macports.org/projects/macports/wiki/MacPortsRenaming And as that's what we'll be handing off to users in the near future we should start documenting it and adapting old documentation to it. I'll correct this one below in a sec... but just for future reference ;-) Regards,,... -jmpp On Jun 28, 2007, at 1:25 AM, source_changes@macosforge.org wrote:
Revision 26541 Author boeyms@macports.org Date 2007-06-27 22:25:27 -0700 (Wed, 27 Jun 2007) Log Message
doc/guide/xml/portfiles: * Correct names of some paths that MacPorts uses. Modified Paths
trunk/doc/guide/xml/portfiles/details.xml Diff
Modified: trunk/doc/guide/xml/portfiles/details.xml (26540 => 26541) --- trunk/doc/guide/xml/portfiles/details.xml 2007-06-28 05:23:48 UTC (rev 26540) +++ trunk/doc/guide/xml/portfiles/details.xml 2007-06-28 05:25:27 UTC (rev 26541) @@ -71,10 +71,10 @@ <term>prefix</term> <listitem> <para>Installation prefix, set in the systemwide - configuration file /etc/ports/ports.conf. Can be + configuration file ${prefix}/etc/ports/macports.conf. Can be overridden on a per port basis. For example XFree86 needs to install in the /usr tree, or aqua applications - are installed in /Applications/Ports</para> + are installed in /Applications/MacPorts</para>
</listitem> </varlistentry> _______________________________________________ macports-changes mailing list macports-changes@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-changes
Hi Juan,
- configuration file /etc/ports/ports.conf. Can be + configuration file ${prefix}/etc/ports/macports.conf. Can be
I see from your commit that it should have been ${prefix}/etc/ macports/macports.conf; could you change that on http:// trac.macports.org/projects/macports/wiki/MacPortsRenaming then (I just copied what was there :-( )? I'd do it myself, but for some reason I'm unable to log in to the parts run by Trac at the moment, though I _can_ log in to the bits run by Wordpress (e.g. www.macosforge.org, www.macports.org). When I try to log in to the Trac-managed bits, it just returns the page that I had before with the same "Register/Login" links in the top-right corner, with no errors or other indications that there had been any problems. Kind regards, Maun Suang -- Boey Maun Suang (Boey is my surname) Email: boeyms at macports dot org
On Jun 29, 2007, at 4:58 AM, Boey Maun Suang wrote:
Hi Juan,
- configuration file /etc/ports/ports.conf. Can be + configuration file ${prefix}/etc/ports/macports.conf. Can be
I see from your commit that it should have been ${prefix}/etc/ macports/macports.conf; could you change that on http:// trac.macports.org/projects/macports/wiki/MacPortsRenaming then (I just copied what was there :-( )?
What I tried to do there was detail how the changes would happen in progress: opt/local/etc/ports/ports.conf -----> /opt/local/etc/ ports/macports.conf /opt/local/etc/ports/dp_version -----> /opt/local/etc/ ports/mp_version /opt/local/etc/ports -----> /opt/local/etc/ macports So that readers would actually catch each and every single change. The last line indeed tells you "/opt/local/etc/ports" becomes "/opt/ local/etc/macports". I added the word "gradual" in "WIth respect to installation paths, a default MacPorts installation upgraded to this branch would experience the following gradual moves:" to try to explain this better, but let me know if you'd like to see an "overall results" box with what will finally be there.
I'd do it myself, but for some reason I'm unable to log in to the parts run by Trac at the moment, though I _can_ log in to the bits run by Wordpress (e.g. www.macosforge.org, www.macports.org). When I try to log in to the Trac-managed bits, it just returns the page that I had before with the same "Register/Login" links in the top- right corner, with no errors or other indications that there had been any problems.
Kind regards,
Hhhhmm, I just logged in right now with no problems. Try some standard debugging techniques like dumping cache, restarting your browser or similar and try again, let me know if you're still experiencing problems.
Maun Suang
Regards,... -jmpp
On 29/06/2007, at 22:49, Juan Manuel Palacios wrote:
What I tried to do there was detail how the changes would happen in progress:
opt/local/etc/ports/ports.conf -----> /opt/local/etc/ ports/macports.conf /opt/local/etc/ports/dp_version -----> /opt/local/etc/ ports/mp_version /opt/local/etc/ports -----> /opt/local/etc/ macports
So that readers would actually catch each and every single change. The last line indeed tells you "/opt/local/etc/ports" becomes "/opt/ local/etc/macports". I added the word "gradual" in "WIth respect to installation paths, a default MacPorts installation upgraded to this branch would experience the following gradual moves:" to try to explain this better, but let me know if you'd like to see an "overall results" box with what will finally be there.
I see, I misunderstood how that was supposed to be read; I had assumed that they were independent, though a closer reading shows that, as a whole, that can't make sense. Perhaps emphasis that the steps are sequential rather than independent would also be in order.
Hhhhmm, I just logged in right now with no problems. Try some standard debugging techniques like dumping cache, restarting your browser or similar and try again, let me know if you're still experiencing problems.
It works okay now from another location; I think I'll have to chalk the problem up to some unfathomable problem caused by my university's brain-dead installation of the Squid caching proxy. For some reason the people employed to actually run my university's network seem far less competent than many of those learning about such things, let alone the staff we have teaching about and researching them. Oh well. Kind regards, Maun Suang -- Boey Maun Suang (Boey is my surname) Email: boeyms at macports dot org
On Jun 30, 2007, at 12:57 PM, Boey Maun Suang wrote:
On 29/06/2007, at 22:49, Juan Manuel Palacios wrote:
What I tried to do there was detail how the changes would happen in progress:
opt/local/etc/ports/ports.conf -----> /opt/local/etc/ ports/macports.conf /opt/local/etc/ports/dp_version -----> /opt/local/etc/ ports/mp_version /opt/local/etc/ports -----> /opt/local/etc/ macports
So that readers would actually catch each and every single change. The last line indeed tells you "/opt/local/etc/ports" becomes "/opt/ local/etc/macports". I added the word "gradual" in "WIth respect to installation paths, a default MacPorts installation upgraded to this branch would experience the following gradual moves:" to try to explain this better, but let me know if you'd like to see an "overall results" box with what will finally be there.
I see, I misunderstood how that was supposed to be read; I had assumed that they were independent, though a closer reading shows that, as a whole, that can't make sense. Perhaps emphasis that the steps are sequential rather than independent would also be in order.
I think your choice of the "sequential" word makes a pretty big difference in making things clearer, included ;-) Thanks for your reviews! Regards,... -jmpp
participants (2)
-
Boey Maun Suang
-
Juan Manuel Palacios