[Adopting a port..or contributing... and a patch included for java on most recent of all jdk/jre)

b. f. bf1783 at googlemail.com
Thu Jun 30 12:08:24 UTC 2011

> Am 30.06.2011 04:23, schrieb xD 0x41:

> *For your next submission*, please keep the information below in mind so
> we can actually use your contribution:
> In a common work flow, you'd usually first update the ports tree (for
> instance, running "portsnap fetch update", or for the first time,
> "portsnap fetch extract"),

Some alternative updating methods (anonymous cvs, cvsup/csup, rsync,
ctm, ftp) are in:


>do "make checksums" on the old port before

a typo, the target is "checksum", no trailing s

(for reference, the targets are documented in the Makefiles in
ports/Mk, and in the PORTS(7) manpage)

> touching the Makefile so that the other and/or old files are there and
> properly downloaded (except if all distfiles change, even if "all" means
> just one)
> To generate the sha256 for the files, all it takes is to download the
> new files, verify it's properly downloaded and untampered (best with
> GnuPG signatures if available), put it in /usr/ports/distfiles (or a
> subdirectory, if specified in the Makefile), and then "make makesums"

a typo, the target is "makesum", no trailing s

> will do the job. That also works outside the ports directory tree, if
> you copy the original port and work on the copy.
> Finally, to ease tracking of your contribution, and make sure it isn't
> lost, it's useful if you
> A. either use the port-tools to submit the patches with the "port
> submit" command as a "PR",

Note that "port" is a utility from the ports-mgmt/porttools port,
which must be installed -- it is not in the base system or in
ports/Tools.  If you are going to use this, consider running "port
test" on your patched port before proposing changes.


More information about the freebsd-ports mailing list