Re: DEBUG does not disable stripping in some ports

[Antoine Jacoutot]

On Sat, May 05, 2012 at 06:16:59PM +0200, Tobias Ulmer wrote:
> > For building ports you're supposed to use
> > SUDO=/usr/bin/sudo -E
> > in /etc/mk.conf
> > 
> > I guess the documentation should be made aware of that... Is using -E 
> > helping in your case?
> 
> Interesting.
> 
> Indeed it does fix my problem. But that seems like a hack because
> sudoers lists all these "unnecessary" ports variables.

Yes because at first people tried to add missing variables but it became 
unmaintainable in the long run because there are just too many with some being 
removed/added.

> > > Index: pkgpath.mk
> > > ===================================================================
> > > RCS file: /home/vcs/cvs/openbsd/ports/infrastructure/mk/pkgpath.mk,v
> > > retrieving revision 1.44
> > > diff -u -p -r1.44 pkgpath.mk
> > > --- pkgpath.mk    17 Feb 2012 07:40:35 -0000      1.44
> > > +++ pkgpath.mk    5 May 2012 15:31:22 -0000
> > > @@ -110,9 +110,9 @@ _cache_fragment = \
> > >  HTMLIFY =        sed -e 's/&/\&amp;/g' -e 's/>/\&gt;/g' -e 's/</\&lt;/g'
> > >  
> > >  _MAKE = cd ${.CURDIR} && PKGPATH=${PKGPATH} exec ${MAKE}
> > > -_SUDOMAKE = cd ${.CURDIR} && PKGPATH=${PKGPATH} exec ${SUDO} ${MAKE}
> > > +_SUDOMAKE = cd ${.CURDIR} && exec ${SUDO} ${SETENV} ${MAKE_ENV} 
> > > PKGPATH=${PKGPATH} ${MAKE}
> > >  _MAKESYS = cd ${.CURDIR} && PKGPATH=${PKGPATH} exec ${_SYSTRACE_CMD} 
> > > ${MAKE}
> > > -_SUDOMAKESYS = cd ${.CURDIR} && PKGPATH=${PKGPATH} exec ${SUDO} 
> > > ${_SYSTRACE_CMD} ${MAKE}
> > > +_SUDOMAKESYS = cd ${.CURDIR} && exec ${SUDO} ${SETENV} ${MAKE_ENV} 
> > > PKGPATH=${PKGPATH} ${_SYSTRACE_CMD} ${MAKE}
> > >  
> > >  REPORT_PROBLEM_LOGFILE ?=
> > >  .if !empty(REPORT_PROBLEM_LOGFILE)
> > > 
> > 
> > -- 
> > Antoine
> > 
> 

-- 
Antoine