Re: pkg/49343: libpurple with option 'perl' fails during packaging when Purple.bs is empty

[David Holland <dholland-pbugs%netbsd.org@localhost>]

The following reply was made to PR pkg/49343; it has been noted by GNATS.

From: David Holland <dholland-pbugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/49343: libpurple with option 'perl' fails during packaging
 when Purple.bs is empty
Date: Sat, 22 Nov 2014 19:52:49 +0000

 On Fri, Oct 31, 2014 at 05:55:00AM +0000, richard%NetBSD.org@localhost wrote:
  > pidgin-2.10.9/libpurple/plugins/perl/common/Makefile has the
  > following 'dynamic' installation snippet:
  > >$(INST_DYNAMIC): $(OBJECT) $(MYEXTLIB) >$(INST_ARCHAUTODIR)$(DFSEP).exists $(EXPORT_LIST) $(PERL_ARCHIVE) >$(PERL_ARCHIVE_AFTER) $(INST_DYNAMIC_DEP)
  > >    $(RM_F) $@
  > >    $(LD)  $(LDDLFLAGS) $(LDFROM) $(OTHERLDFLAGS) -o $@ $(MYEXTLIB) \
  > >      $(PERL_ARCHIVE) $(LDLOADLIBS) $(PERL_ARCHIVE_AFTER) >$(EXPORT_LIST)    \
  > >      $(INST_DYNAMIC_FIX)
  > >    $(CHMOD) $(PERM_RWX) $@
  > >    $(NOECHO) $(RM_RF) $(BOOTSTRAP)
  > >    - $(CP_NONEMPTY) $(BOOTSTRAP) $(INST_BOOT) $(PERM_RW)
  > 
  > where CP_NONEMPTY is defined as:
  > >CP_NONEMPTY = $(ABSPERLRUN) -MExtUtils::Command::MM -e 'cp_nonempty' --
  > 
  > Perhaps adding a variable for PLIST testing for Purple.bs being
  > present is a solution. Currently PLIST uses the following for
  > Purple.bs:
  > >${PLIST.perl}lib/purple-2/perl/auto/Purple/Purple.bs
 
 Would it be wrong to patch it to always install Purple.bs even if it's
 empty? (I have no idea what the file is or what it does...)
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost