On 5 May 2007, at 20:41, source_changes@macosforge.org wrote:
Revision 24832 Author jberry@macports.org Date 2007-05-05 17:41:51 -0700 (Sat, 05 May 2007) Log MessageStore readline history in ~/.macports/.history instead of ~/.port_history
Why ~/.macports/.history and not ~/.macports/history (why a .file in a .dir)? And while I'm asking why not use ~/Library/Application Support/ Macports instead of ~/.macports? Isn't it the Apple way to use the Library instead of .dirs?
Modified Paths trunk/base/src/port/port.tcl Diff Modified: trunk/base/src/port/port.tcl (24831 => 24832) --- trunk/ base/src/port/port.tcl 2007-05-06 00:35:02 UTC (rev 24831) +++ trunk/base/src/port/port.tcl 2007-05-06 00:41:51 UTC (rev 24832) @@ -2434,13 +2434,14 @@ proc process_command_file { in } { global current_portdir + global darwinports::autoconf::macports_user_dir # Initialize readline set isstdin [string match $in "stdin"] set name "port" set use_readline [expr $isstdin && [readline init $name]] - set history_file [file normalize "~/.${name}_history"] - + set history_file [file normalize "${macports_user_dir}/.history"] + # Read readline history if {$use_readline} { rl_history read $history_file _______________________________________________ macports-changes mailing list macports-changes@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-changes
Randall Wood rhwood@mac.com http://shyramblings.blogspot.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
Hi Randall, On May 5, 2007, at 5:53 PM, Randall Wood wrote:
On 5 May 2007, at 20:41, source_changes@macosforge.org wrote:
Revision 24832 Author jberry@macports.org Date 2007-05-05 17:41:51 -0700 (Sat, 05 May 2007) Log MessageStore readline history in ~/.macports/.history instead of ~/.port_history
Why ~/.macports/.history and not ~/.macports/history (why a .file in a .dir)?
Well, my reasoning may have been a bit lame, but it seemed like since it's not normally a file anybody wants to read (while there are other files in ~/.macports that they do) that it was just as well to keep it hidden and out of the way.
And while I'm asking why not use ~/Library/Application Support/ Macports instead of ~/.macports? Isn't it the Apple way to use the Library instead of .dirs?
Very good question. I'd be happy to hear feedback from other developers. I'd happy with either.
Modified Paths trunk/base/src/port/port.tcl Diff Modified: trunk/base/src/port/port.tcl (24831 => 24832) --- trunk/ base/src/port/port.tcl 2007-05-06 00:35:02 UTC (rev 24831) +++ trunk/base/src/port/port.tcl 2007-05-06 00:41:51 UTC (rev 24832) @@ -2434,13 +2434,14 @@ proc process_command_file { in } { global current_portdir + global darwinports::autoconf::macports_user_dir # Initialize readline set isstdin [string match $in "stdin"] set name "port" set use_readline [expr $isstdin && [readline init $name]] - set history_file [file normalize "~/.${name}_history"] - + set history_file [file normalize "$ {macports_user_dir}/.history"] + # Read readline history if {$use_readline} { rl_history read $history_file _______________________________________________ macports-changes mailing list macports-changes@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-changes
Randall Wood rhwood@mac.com http://shyramblings.blogspot.com
"The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
On 05 May, 2007, at 22:04, James Berry wrote:
On May 5, 2007, at 5:53 PM, Randall Wood wrote:
Why ~/.macports/.history and not ~/.macports/history (why a .file in a .dir)?
Well, my reasoning may have been a bit lame, but it seemed like since it's not normally a file anybody wants to read (while there are other files in ~/.macports that they do) that it was just as well to keep it hidden and out of the way.
I'd just as soon have it visible. On the off chance I _did_ want to look at it, I'd never have thought to look for a dot-file there.
And while I'm asking why not use ~/Library/Application Support/ Macports instead of ~/.macports? Isn't it the Apple way to use the Library instead of .dirs?
Very good question. I'd be happy to hear feedback from other developers. I'd happy with either.
I would say that, in an ideal world, MacPorts configuration would go in Application Support instead of a dot-file. However, almost everything that MacPorts installs has its configuration in dot-files. It would be inconsistent to put MacPorts configuration in a different place from all of these. So, unless someone wants to patch all of the ports to use Application Support too, I think ~/.macports/ is better Chris
Why ~/.macports/.history and not ~/.macports/history (why a .file in a .dir)?
Well, my reasoning may have been a bit lame, but it seemed like since it's not normally a file anybody wants to read (while there are other files in ~/.macports that they do) that it was just as well to keep it hidden and out of the way.
I'd just as soon have it visible. On the off chance I _did_ want to look at it, I'd never have thought to look for a dot-file there.
+1 from me on the latter view; furthermore, every other program that I've run that made a ~/.blah directory (elinks, mplayer, gnupg, subversion, tor, ssh, wireshark, etc., etc.) creates all its files in ~/.blah without a leading dot.
And while I'm asking why not use ~/Library/Application Support/ Macports instead of ~/.macports? Isn't it the Apple way to use the Library instead of .dirs?
Very good question. I'd be happy to hear feedback from other developers. I'd happy with either.
I would say that, in an ideal world, MacPorts configuration would go in Application Support instead of a dot-file. However, almost everything that MacPorts installs has its configuration in dot- files. It would be inconsistent to put MacPorts configuration in a different place from all of these.
To me, Library/Application Support is the place where Cocoa apps put things, while Unixish apps, especially command-line ones, use dot- files and dot-directories, so I'd stick with ~/.macports. Kind regards, Maun Suang -- Boey Maun Suang (Boey is my surname) Email: boeyms@macports.org
participants (4)
-
Boey Maun Suang
-
Chris Pickel
-
James Berry
-
Randall Wood