| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}.
- Bump PORTREVISION for ports intalling files in ${X11BASE}.
Notes:
svn path=/head/; revision=191544
|
| |
|
|
|
|
|
| |
Reported by: portscout
Notes:
svn path=/head/; revision=184815
|
| |
|
|
|
|
|
| |
Reported by: portscout
Notes:
svn path=/head/; revision=165836
|
| |
|
|
|
|
|
| |
Approved by: krion@
Notes:
svn path=/head/; revision=154141
|
| |
|
|
|
|
|
|
| |
- Don't mkdir ${JAVAJARDIR} as it has been part of mtree for more than 3 years
- Don't mkdir ${DOCSDIR} twice
Notes:
svn path=/head/; revision=139588
|
| |
|
|
| |
Notes:
svn path=/head/; revision=126623
|
|
|
JSAP parses your command line and instantiates objects of types you specify
based upon that command line. If you configure JSAP to expect an Integer on the
command line, and the user does not provide a String that can be converted to
an Integer, JSAP will alert your program to the fact that there was a problem
with the command line. If JSAP indicates that your command line was
successfully parsed, you are guaranteed an Integer when you request that
parameter's value from your program. There's a pretty big (and growing) list of
return types supported by JSAP.
WWW: http://http://www.martiansoftware.com/jsap/index.html
Notes:
svn path=/head/; revision=126621
|
