Yes, my first post was intended as bug report, but after your answer I've thought the problem may be on my side Thanks for your assistance.

Well, it is a valid bug report because that code need to be fixed by default. Time to start bugging _PN_boy about it again.

New version: v1.6.1
CHANGELOG:
fix auto dotnew handling
option noautodotnew added, to don't include the auto dotnew handling
added check for sourcetemplate

How do we use this option in the ZENBUILD?

First of all: It's nice to see that buildpkg is still alive and kicking and that you are putting such effort into it.
But I feel like buildpkg is getting way bloated and ovely complex. It has multiple different options that influence the build process that it is no longer straight forward to see what is going on. I think you either need to write up exceptional wiki and man entries or just simplify buildpkg by removing some options.
Package builders are not stupid and should be able to manage with with a build{ } part. If I recall correctly the intention of buildpkg was to automate the redundant and tedious chores like stripping and tgzing...

the only change from 1.6.0 and 1.6.1 is that one more advanced option was added (and the feature added in 1.6.0 should now be corrected).
The default behavior is, as it should be, files in etc are user global files and should never be substituted.

the 'noautodotnew' option is available in the man page(man ZENBUILD), the options that have been added are to be considered advanced, and are usually not required

Regards,
Pedro Pinto

So, let me understand. If I have a package that installs files in the /etc branch that should not be dotnewed (i.e. VirtualBox), I should included the following in ZENBUILD

Suppose there is a packages that installs files in the /etc branch where some should be dotnewed and others not, should the ZENBUILD look like this?

If this is true, then for me, the options=('noautodotnew') will be a default in my ZENBUILDs, effectively resulting in the functionality of buildpkg before the 1.6 version. I want to learn and understand which files added to /etc branch need to be dotnew and which don't. The auto dotnew feature doesn’t afford me that opportunity.
Regards
Rich

Your understanding is correct Rich.

What about introducing a new switch to use depfinder instead of requiredbuilder if flatdeps wasn't selected?

Though I did a patch it's not the best way to patch/unpatch buildpkg depending on what I need. BTW this is the patch I'm talking about, to clarify a bit what I mean:
http://gaia.homelinux.org/buildpkg-depfinder.patch

I would be really happy to see that new feature.

I, for one, love the direction buildpkg has gone. Sure, I don't use most of the options, but they don't hurt either. And things like moving .desktop files to the correct directory automatically is just plain smart, it reduces errors and speeds things up for the packager.

It's better to have an exception for....exceptional packages than to have mistakes for common packages.

buildpkgcreator has some good points.

I think as long as those automatic helpers can be disabled it's no problem. Furthermore especially that every file in /etc will become dotnew per default is quite handy and speeds up the build process a lot. In case files shouldn't be dotnew you can disable it and do it manually. But I think for most packages that's not needed.
IMO it's a really good tool and in case you want to have more control about what happens exactly, just let it create a buildfile and edit that one like I do for fusion-icon which is downloaded from git.

So thanks, for that really good tool. It safes me (and you) a lot of work.

For me it is easy and there really aren't that many options. Compar man sshd_config and man ZENBUILD. There's a big difference.

Hi,



+1
I just took a look at the man and it's not so scary.