[Bug 220978] mail/dcc-dccd mixes data and code, offends hier(7)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Jul 24 20:17:36 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220978

            Bug ID: 220978
           Summary: mail/dcc-dccd mixes data and code, offends hier(7)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: mi at ALDAN.algebra.com
                CC: pkubaj at anongoth.pl
                CC: pkubaj at anongoth.pl
             Flags: maintainer-feedback?(pkubaj at anongoth.pl)

Created attachment 184675
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184675&action=edit
do it

The current version of the port mixes together the scripts/binaries and the
data. Maintaining read-only ${PREFIX} becomes impossible because the port tries
to change ${PREFX}/dcc/map and other data.

Fortunately, vendor's configure allows for the "home directory" to be different
from where the executables are...

The attached patch does the following:

 1. Introduces the DCCDATA knob pointing at /var/dcc (which is the vendor's
default)
 2. Changes the destination of data files throughout the port to point there
 3. Changes port's own ${PREFIX}/dcc/libexec to simply ${PREFIX}/libexec -- as
hier(7) suggests
 4. Teaches vendor's Makefiles to use "install -s" instead of strip-ing in the
port's post-install
 5. Eliminates the vendor's own MD5 implementation -- the code is already
linked with our -lmd, but was *still* compiling its own md5.c

Potential further improvements:
 . Change the various scripts in the port's files/*.in to share the single
dcc_home-knob instead of each script looking for its own foo_home
 . Find a better location for cgi-bin -- ${PREFIX}/www ?

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list