Re: pkg/47488: textproc/xalan-c got removed; find replacement in wip/xalan-c

[Noud de Brouwer <noud4%home.nl@localhost>]

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

From: Noud de Brouwer <noud4%home.nl@localhost>
To: gnats-bugs%netbsd.org@localhost, c-users%xalan.apache.org@localhost, 
dev%xalan.apache.org@localhost
Cc: is%netbsd.org@localhost, pkg-manager%netbsd.org@localhost, 
gnats-admin%netbsd.org@localhost, 
 pkgsrc-bugs%netbsd.org@localhost, tech-pkg%netbsd.org@localhost
Subject: Re: pkg/47488: textproc/xalan-c got removed; find replacement in
 wip/xalan-c
Date: Fri, 01 Feb 2013 20:53:53 +0000

 On Fri, 2013-02-01 at 21:11 +0100, is%netbsd.org@localhost wrote:
 > On Fri, Feb 01, 2013 at 07:12:27PM +0000, Noud de Brouwer wrote:
 > 
 > To: gnats-bugs%netbsd.org@localhost, c-users%xalan.apache.org@localhost, 
 > dev%xalan.apache.org@localhost       
 > Cc: pkg-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
 > pkgsrc-bugs%netbsd.org@localhost,     
 >         tech-pkg%netbsd.org@localhost                                        
 >              
 > Subject: Re: pkg/47488: textproc/xalan-c got removed; find replacement in    
 >    
 > 
 > (...)
 > 
 > This is *so* wrong in so many respects.
 > 
 > tech-pkg is about pkgsrc *infrastructure* (basically - pkgtools, the mk
 
 the procedures are part the infrastructure.
 -- noud
 > subtree, and maybe generic methods to access shells, compilers, language
 > interpreters etc for the purpose of building or executing pkgsrc-built
 > software. It's wrong most of the time when you write about individual 
 > packages.
 > 
 > gnats-bugs is for replying to existing PRs. It should not be intermixed
 > with external traffic, as it will make the noted PR unreadable.
 > 
 > pkgsrc-bugs is for followups to such gen generic instructions
 > 
 > the -admin is the sender address for gnats' messages about PR changes.
 > 
 > Using all at once is bad, especially intermixed with messages to outside
 > people/lists.
 > 
 > If you want to clarify a software's status, please do so and
 > summarize results to the referring PR if one exists, or to tech-pkg
 > *or* pkgsrc-users (depending of what seems more appropriate) or maybe
 > the noted package maintainer.
 > 
 > Regards,
 >      -is