-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello and thanks a lot, I am a beginner with debian-packaging and to tell you the truth, bringing my packages into official debian-repositories does not have priority, but I felt it would be the correct way to do it, using a metapackage. We are in fact planning to make binary images using preseeding and metapackages in KVM-machines. It is not only one package either, but a 32- and a 64- bit version. For me the question remains, how to integrate configuration-changes, for Privoxy for instance, what is the simplest most common way for that, use debconf or cfengine or just package the conf-file into the metapackage, would this violate debian-policies? Greetings Andreas On Wed, 26 Oct 2016 16:30:56 +0200 Andreas Tille <[email protected]> wrote: > From: Andreas Tille <[email protected]> > To: Andreas Glaeser <[email protected]> > Cc: [email protected] > Subject: Re: blends-doc Appendix B > Date: Wed, 26 Oct 2016 16:30:56 +0200 > User-Agent: Mutt/1.5.23 (2014-03-12) > > Hi Andreas, > > On Wed, Oct 26, 2016 at 03:38:11PM +0200, Andreas Glaeser wrote: > > I have sent them already, my message had five attachments, see attachments. > > > > I'm sorry, I simply missed these. > > > I feel I am not welcomed by the debian-community, nor helped whatsoever. > > I feel not really motivated to help if somebody claims not to get help > due to a simple oversight of the one who voluntered to help in a quite > timely manner. I'm sorry, but may be you should be more patient. > > I've checked your files and your debian/changelog file was full of > syntactical errors. I'd recommend you should use dch to edit this file > to avoid this kind of problems. > > Moreover I've added a debian/rules file and a Makefile (both unchanged > from the blends-dev example). The attached source tarball is the result > of a `make dist`. > > As a conclusion I would not subscribe your statement that blends-dev > examples are wrong. My question whether you *really* want to create > a Blend if you want to create a single metapackage remains. > > Hope this helps > > Andreas. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlgS7zYACgkQ5+rBHyUt5wvIRQCbBmuNxCjRzXVJHahdklgZqaDq dukAoLO/l7GmUF8OCe57YVjOm8zl+hH3 =4UKb -----END PGP SIGNATURE-----
