DragonFlyBSD

I must say that I haven't understood your first question.

Regarding the second one, that usually happens if you don't cleanly unmount the
ufs /boot or so. It should not happen normally (and it doesn't, as far as I've
seen)

And to answer your third question:
pkgsrc patches should be posted on netbsd's pkgsrc bugtracker and should adhere
to their standards, which I know nothing about and you should check with them
anyways.
DragonFly patches should adhere to style(9), be split up sensibly (i.e. don't
put 10 completely different things into one diff) and be in unified diff format,
preferably the output of git format-patch.

Cheers,
Alex

1 dec 2010 kl. 13.41 skrev Alex Hornung (via DragonFly issue tracker):
...

And to answer your third question:
pkgsrc patches should be posted on netbsd's pkgsrc bugtracker and should adhere
to their standards, which I know nothing about and you should check with them
anyways.

...

Patches that touch the software itself could go upstream to third part directly. Depending on the pkgsrc packager it can take some time for it to get into pkgsrc though. I prefer this way as it keeps vanilla code usable outside pkgsrc.

Sometimes smaller changes to the build must be made though... See http://www.NetBSD.org/cgi-bin/sendpr.cgi?gndb=netbsd

Max

Yes, true, software patches ideally go upstream. I'd generally advise against
patches for pkgsrc.

Regards,
Alex