[Bug 193183] [STAGE] net/beacon: Request MAINTAINERship, pkg-descr cleanup

[bugzilla-noreply at freebsd.org]

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

--- Comment #36 from C Hutchinson <portmaster at bsdforge.com> ---
(In reply to John Marino from comment #35)
> I don't get your fix at all:
> 
> ${FIND} ${STAGEDIR} -name 'perllocal.pod' -delete
> ${FIND} ${STAGEDIR} -name 'perllocal.pod.gz' -delete
> 
> I have a lot of questions.
> 1) it either ends in pod or pod.gz, why do you cover both bases?  obviously
> one command is never used
> 2) why are you using find?  How many files are there?
> 
> If the answer is "1", then use ${RM} ${STAGEDIR}${PREFIX} .... instead

I _knew_ this question was coming. So why didn't I address it
beforehand?
OK. Indeed, a _pertinent_ question. I was puzzled, myself. Here's
how it went;

${FIND} ${STAGEDIR} -name 'perllocal.pod' -delete

check-plist complains that perllocal.pod.gz is orphaned.
Crap! That's right. I don't have that man-compressed: nonsense in
there, anymore.

${FIND} ${STAGEDIR} -name 'perllocal.pod.gz' -delete

check-plist complains about perllocal.pod being orphaned. Grr...

Fine! It looks silly. But let's see how it flies;

${FIND} ${STAGEDIR} -name 'perllocal.pod' -delete
${FIND} ${STAGEDIR} -name 'perllocal.pod.gz' -delete

No complaints from either check-plist, or portlint.
I'm growing weary of all this, by now. So begrudgingly, I submit it.

<sigh> I'll poke at it some more, and see if I can better determine
the issue. I _suspect_ it's because both files existed, at one time.
So pkg, or make preserved that information.

I'll get back with something more elegant. :)

--Chris

P.S. I got the ${FIND} script out of Mk/Uses/perl5.mk
It is used to clobber empty .bs files.

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