5 Commits

Author SHA1 Message Date
zhuk
28a1c15db0 Unbreak portimport after previous. Clean up getopts call while there. 2014-02-09 15:10:49 +00:00
zhuk
2f6834a234 Face the reality: portcheck(1) is heavily used now, and not only for new
ports. Given that you import port once but update it a few times, make
the update mode (-CU) default for portcheck, and provide a "new port"
switch (-N) instead.

This commit updates portcheck(1) and portimport(1): code, documentation and
tests. The WWW stuff will be updated separately.

Note: regression suite fails now as it detected an actual misconsistence
in portcheck's output. This will be handled ASAP, too.

Initial prodding by naddy@
2014-02-04 21:18:14 +00:00
zhuk
1d58015f11 Now that we have portcheck(1), start relying on it instead of doing
the checks and pkgpath detection ourself in portimport(1).

Sitting on this diff since september, reminded by kirby@.

Tested in the wild by importing many ports, mostly KDE4-related.

Input and okay sthen@

(now committing the right file instead of ports/bin/portcheck)
2013-12-11 16:11:09 +00:00
zhuk
7f00acb024 Add -u option to portimport(1), allowing to specify your username in CVS.
BUGS section is gone now.
2013-04-11 15:18:00 +00:00
rpe
e195d5e0df add portimport
portimport is used to import the directories and files of a new
port to the OpenBSD ports cvs(1) repository, avoiding common mistakes.
It has to be executed from within the new port's directory.

please read the BUGS section in portimport(1) for details about the
user login used to connect to cvs.openbsd.org !!

addition suggested by and OK sthen@
no objections from jasper@ espie@ aja@
manpage nits jmc@
2013-04-09 19:51:37 +00:00