using in mk.conf, especially a bunch of .poison lines for common typos,
including suggestions from aja, espie, naddy and others. Can be used
with .include in mk.conf.
oks from at least william@ phessler@ and several users like it too.
Currently one needs protective glasses to read a random README; so new
READMEs should be in line with the simple "rules" layed out here.
OK aja@ naddy@ sthen@
From now on, building ports requires X11BASE.
* lots of ports missed this variable (porters always have X11 installed)
jasper made a first pass on fixing these, but no doubt it will drift
away soon
* users should use packages
* people building ports should know what they are doing and having
X11BASE as a requirement is perfectly reasonnable
* we are merging config.x11.site into config.site because of a stupid
autofoo bug ; currently when USE_X11 is set, some ports may loose the
ability to even load config.site
tested on a bulk by landry@
ok robert@ jasper@ landry@ sthen@ naddy@ "I won't cry if it dies" espie@
This was only used in two ports, and will never be used in more ports
as GitHub no longer builds new gems. Both of the ports are also
found on rubygems.org, so this switches them to use the standard
MASTER_SITE_RUBYGEMS from ruby.port.mk. ruby-findmyiphone has a small
change from the GitHub version that requires a package bump.
OK landry@
Gemcutter was replaced with rubygems.org, so remove the MASTER_SITES
from the Makefiles and let MASTER_SITE_RUBYGEMS in ruby.port.mk
handles things.
OK sthen@ "if the checksums still match"
bunch of mirrors when the most common problem is that a distfile has been
moved to the archive; ok jasper@
- while there replace planetmirror (no longer active) with another site
- add some new sites to replace the above
- switch some sites over to using http - notably, the first
site on the list is now http, which is a big win on networks with
broken ftp (note that peek-ftp skips http mirrors, so this doesn't
cause any problem there).
okay ajacoutot@