Changes between Initial Version and Version 1 of MaintainingAPort

Timestamp:

Dec 10, 2006, 3:15:35 PM (17 years ago)

Author:

rhwood@…

Comment:

Create the page

MaintainingAPort

@@ +1 @@
+== Source ==
+To be removed once all major points in this email are covered.
+{{{
+        From:     john_owens@yahoo.com
+        Subject:        my first port - how to
+        Date:   10 December 2006 08:48:13 EST
+        To:       macports-users@lists.macosforge.org
+
+Greetings, I'm attempting to write my first port. Writing the portfile
+is not too difficult, as there's lots of good examples. However,
+actually making it install is a lot tougher.
+
+I am making it work by:
+
+- adding the portfile in the right place in /opt/local
+- changing the portindex file to add the port info manually (and
+  making up a number for it)
+
+However, these things seem really kludgey. Is it not possible to
+have a local portfile somewhere and install it using a command
+line "port" command? That would seem much better, but I can't find
+any documentation on how that's done. (For instance, there's a 
+local "~/.portsrc" file? but I can't find any docs on it.)
+
+I think this is the sort of thing that really ought to be on the
+wiki - the barrier to entry of adding a portfile is really very
+high, and a short guide would be helpful. What it should say:
+
+- "So you've written a Portfile. Here's how you test it locally."
+  - "Here's how you prevent it from being clobbered when you
+     selfupdate."
+  - "Here's where you put it if you're testing it locally, and want
+    to leave it local for a while."
+- "Your Portfile is awesome. It works. Here's how to add it to
+  the MacPorts repository."
+  - "... and here's how you update it."
+- "Your Portfile probably has lots of dependencies. Here's how
+  you tell what they are." 
+- "Here are naming conventions for ports."
+
+etc.
+
+Especially the first one right now would be very useful for me.
+
+JDO
+}}}