[MacPorts] #15395: Use primary port category for fetched distfile layout

[MacPorts]

#15395: Use primary port category for fetched distfile layout
----------------------------------+-----------------------------------------
  Reporter:  wsiegrist at apple.com  |       Owner:  wsiegrist at apple.com       
      Type:  enhancement          |      Status:  new                       
  Priority:  Normal               |   Milestone:  MacPorts base enhancements
 Component:  base                 |     Version:                            
Resolution:                       |    Keywords:  fetch mirror distfiles    
----------------------------------+-----------------------------------------
Comment (by ryandesign at macports.org):

 @afb: I was looking for something like "{{{port dist}}}" recently. Didn't
 know it had been considered before. Would love to see it implemented!

 @wsiegrist: I would tend to vote against the change proposed in this
 ticket, because I don't see a benefit, and I do see many opportunities for
 problems as a result, as already discussed in this ticket and by email.
 (Orphaned distfiles or needing a migration script, {{{dist_subdir}}} being
 manipulated by many ports already which would break.) Also, I "{{{cd}}}"
 to my various ports' distfiles directories fairly often, and it's already
 quite enough typing to get there without having the additional category
 directory name, not to mention that I don't always remember my ports'
 categories. For the portfiles, I'm a big fan of "{{{port cddir foo}}}" (my
 local alias for "{{{cd `port dir foo`}}}") and why I'd love a "{{{port
 dist foo}}}" (for which I could write an alias "{{{port cddist foo}}}" to
 do "{{{cd `port dist foo`}}}").

-- 
Ticket URL: <http://trac.macports.org/ticket/15395#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS