On Thu, Nov 05, 2015 at 10:13:48AM -0800, Philip Guenther wrote:
On Thu, Nov 5, 2015 at 4:18 AM, Stuart Henderson <[email protected]> wrote:
On 2015/11/05 11:42, Tati Chevron wrote:
>Is there some reason to not simply use the packages though? You'll end up
>with a lot less junk installed on your system than building it yourself.
I need to patch the mutt source to improve handling of keyboards with
keys beyond F12. For example, at the moment adding bindings for F15-F24
fails.
Fair enough. Things will go a bit smoother if you pkg_add the build
dependencies though (libidn, lynx, docbook-xsl, qdbm)
I'll throw a quick thumbs-up for adding FETCH_PACKAGES=yes to your
mk.conf to have the ports infrastructure automatically install
dependencies instead of building them.
Out of interest, is there a, (simple), way to use the ports infrastructure to
just fetch the source for a particular port, _and it's dependencies_, without
building it?
Or to be more general - what is the best way to manage a local copy of the
distfiles archive?
Doing a make checksum in /usr/ports pulls about 25 GB of source, which just
about fits on a single layer BD-R, and then allows you to travel far away from
an internet connection, and still be confident that you have everything you
might need.
The problem comes when updating it, (assuming that you are following each new
-release), it might not be convenient/possible/desirable/efficient to start
with an empty /usr/ports/distfiles and pull another 25 GB to populate it, and
infact wasn't convenient for me last time, so I just manually fetched the most
important changed distfiles, and added them to those of the previous release.
Given a full set of distfiles for, (for example), 5.5-release, which also has
some for 5.6-release and 5.7-release mixed in, what is the best way to separate
out those which are now obsolete?
Also, the PERMIT_PACKAGE_CDROM tag in the makefiles doesn't seem to follow any
standard format. As well as, 'yes', and, 'no', there are entries that say
things like, 'Stupid license', 'no fee', 'non-commercial use only', etc. There
doesn't seem to be any way of automatically parsing the makefiles to eliminate
distfiles which cannot legally be distributed on CD-ROM.
--
Tati Chevron
Perl and FORTRAN specialist.
SWABSIT development and migration department.
http://www.swabsit.com
