(I think we're both subscribed to the list; I'll drop the CC stuff.)
;)
On Mon, Mar 26, 2007 at 12:08:32PM -0500, [EMAIL PROTECTED] wrote:
> On 25 March 2007 at 14:43, Will Maier <[EMAIL PROTECTED]> wrote:
> > c) update-plist fails; do you need @sample stuff in the PLIST?
> > ===> Updating plist for radmind-1.8.0
> > Bogus element outside of every prefix: /usr/ports
> > Bogus element outside of every prefix: /usr/ports/sysutils
> > Bogus element outside of every prefix: /usr/ports/sysutils/radmind
> > Bogus element outside of every prefix:
> > /usr/ports/sysutils/radmind/w-radmind-1.8.0
> > Bogus element outside of every prefix:
> > /usr/ports/sysutils/radmind/w-radmind-1.8.0/fake-i386
> > Bogus element outside of every prefix:
> > /usr/ports/sysutils/radmind/w-radmind-1.8.0/fake-i386/var
> > Bogus element outside of every prefix:
> > /usr/ports/sysutils/radmind/w-radmind-1.8.0/fake-i386/var/radmind
> > Bogus element outside of every prefix:
> > /usr/ports/sysutils/radmind/w-radmind-1.8.0/fake-i386/var/radmind/cert
> > Bogus element outside of every prefix:
> > /usr/ports/sysutils/radmind/w-radmind-1.8.0/fake-i386/var/radmind/client
> > Bogus element outside of every prefix:
> > /usr/ports/sysutils/radmind/w-radmind-1.8.0/fake-i386/var/radmind/postapply
> > Bogus element outside of every prefix:
> > /usr/ports/sysutils/radmind/w-radmind-1.8.0/fake-i386/var/radmind/preapply
>
> Argh, I thought I fixed that... new diff at:
>
> http://openbsd.rutgers.edu/radmind-1.8.0.diff
Looks better; I added the following to make the update-plist target
less unhappy:
post-install:
rm -rf ${DESTDIR}/var/radmind
I bet there's a more clever way to do it, but since those
directories are all empty, I don't see the harm in zapping them.
pkg_add creates and destroys the real /var/radmind as expected on
install and uninstall, respectively.
> I also caught more str* that slipped through (I must not have made
> .orig files before editing them...)
I know this is an issue with the cfengine port, too, and I don't
like strcpy and friends any more than the next guy, but all those
patches seem like wasted effort unless they're destined upstream.
Based on the last few discussions we've had here[0][1], I think it
would be a good idea to remove those patches (or at least not add to
the pile).
Am I misinterpreting mbalmer@ and espie@ on this? Is the current
best-practice "stop adding str* patches to new ports"? or "remove
useless str* patches from existing ports"?
[0] http://marc.info/?l=openbsd-ports&m=117423891123405&w=2
[1] http://marc.info/?l=openbsd-ports&m=117423814822512&w=2
--
o--------------------------{ Will Maier }--------------------------o
| web:.......http://www.lfod.us/ | [EMAIL PROTECTED] |
*------------------[ BSD Unix: Live Free or Die ]------------------*
