[MacPorts] #44882: [developer] kdelibs4 4.14/git/master portfile and directory

[MacPorts]

#44882: [developer] kdelibs4 4.14/git/master portfile and directory
--------------------------+--------------------------------
  Reporter:  rjvbertin@…  |      Owner:  macports-tickets@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:  haspatch
      Port:  kdelibs4     |
--------------------------+--------------------------------

Comment (by larryv@…):

 Replying to [comment:9 rjvbertin@…]:
 > First off, and I'm sorry if that wasn't clear, this is NOT
 > a submission for a new port, or for an upgrade of an existing port to
 > be included in an upcoming release. I've uploaded it hoping to help
 > others working on KDE on OS X, allowing them to grab the port
 > directory from here, install it in their local port registry and then
 > use it. That's why I labelled it as an enhancements instead of a If
 > there's a more appropriate place to put this kind of thing online I'm
 > happy to use that, but in the meantime I thought there's little harm
 > putting it here.

 Ah. Perhaps a wiki page linked from [[KDE]] might work better? It would
 also be editable :)

 > - The revision number is indeed the date of the commit expected in the
 >   local git clone. The result is that the copy of the clone that
 >   MacPorts makes has an invariant name. I find that makes for an easier
 >   workflow if you're making modifications in the local git clone and
 >   then copy them into MacPort's copy before rebuilding.

 The problem there (and this is why we don’t abuse `revision` like this) is
 that we want to divorce upstream versions from Portfile versions, so to
 speak. If you use `revision` as part of your upstream version, there’s no
 way to distinguish whether a revbump is due to a Portfile adjustment or an
 upstream change, short of looking at the Subversion log. So any version
 information that pertains to the software being packaged should be
 entirely contained in `version`.

 > - That local git clone. Remember that this is a port aimed at other
 >   developers. Indeed I could have put a reference to the remote repo
 >   there, but one way or another those other developers are probably
 >   going to want change it for a reference to their own local git clone
 >   ... so I put in a reference to a reasonable location.

 Another benefit of a wiki page would be that you could clearly spell out
 these special requirements and procedures. Perhaps even provide step-by-
 step instructions for getting set up. Or anything you’d like!

-- 
Ticket URL: <https://trac.macports.org/ticket/44882#comment:10>
MacPorts <http://www.macports.org/>
Ports system for OS X