Date: Mon, 23 Jun 1997 22:47:07 -0700 (PDT) From: asami@cs.berkeley.edu (Satoshi Asami) To: scott@statsci.com Cc: freebsd-ports@FreeBSD.ORG Subject: Re: ports/3922: nmh port updated to nmh-0.15 Message-ID: <199706240547.WAA04632@silvia.HIP.Berkeley.EDU> In-Reply-To: <m0wfZn0-0007RRC@plum.statsci.com> (message from Scott Blachowicz on Sat, 21 Jun 1997 16:41:54 -0700)
next in thread | previous in thread | raw e-mail | index | archive | help
* name in the path where 'cvs diff' doesn't. Is there a preference by those * applying patches to the master ports sources as to where the filenames should * be relative to? (i.e. apply with 'patch -p1' or 'patch -p' or whatever? Should * I strip the "nmh-port/" prefix out of my patch here?) I find it easier to have it without the pathname (that way you don't even need a "-p") but if that's the way cvs wants to generate diffs, that's no big deal. (If someone screws up and edits the wrong line, that would be much more hassle. ;) * Also, in general, would the above be better expressed as a pkg/INSTALL script * using ${PKG_PREFIX} & expanding it to give the real full paths to the files? * Or should I not bother with letting the installer know that some files might * need site-customizations? You certainly should. I usually just put "/usr/local" there, if the user knows enough to install the port elsewhere, I'm sure he is smart enough to figure out where the setup file moved. :) Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706240547.WAA04632>