Re: sysutils/krusader: update to 2.8.1

[Robert Bagdan <kikadf.01%gmail.com@localhost>]

I read https://www.pkgsrc.org/wip/users/, and add COMMIT_MSG to
pkgsrc-wip/krusader
(https://github.com/NetBSD/pkgsrc-wip/commit/d218deb2e6a09f854efaccdcbf2d8640e4f2d31d).
I see it is available in pkgsrc-wip/krusader folder, without the
others (Makefile, PLIST etc)
Maybe Thomas had an outdated pkgsrc-wip tree? :)

On Mon, Jul 29, 2024 at 3:46 PM Greg Troxel <gdt%lexort.com@localhost> wrote:
>
> Robert Bagdan <kikadf.01%gmail.com@localhost> writes:
>
> > Do you mean a git commit with the changes in pkgsrc-wip?
> > eg:
> > Import package from pkgsrc to pkgsrc-wip, commit(&push).
> > Changes in pkgsrc-wip, commit&push.
>
> The request is to produce a COMMIT_MSG file which can be used with
>
>   cvs commit -F COMMIT_MSG
>
> after copying the files into the cvs dir.
>
> See
>
>   https://www.pkgsrc.org/wip/users/
>
> specifically:
>
>   Differences from pkgsrc
>
>   A wip package should have a file COMMIT_MSG that contains exactly the
>   text that should be used if importing the package to main pkgsrc, or in
>   updating the main pkgsrc package from the wip version. Someone with main
>   pkgsrc write access should be able to copy bits and do cvs commit -F
>   COMMIT_MSG. This means that it should start off with "category/pkgpath:
>   Add foo version 1.2.3" and then contain the rest. Or "category/pkgpath:
>   Update foo to 4.5.6", a blank line, a description of packaging changes,
>   another blank line, and a summary of what upstream should have put in
>   NEWS.
>
>   Generally, for a package that also exists in pkgsrc, when you update a
>   wip package to a new version, you should also modify COMMIT_MSG so that
>   it additionally includes the upstream changes for the new version. If
>   the package is not in pkgsrc, then COMMIT_MSG says "Add" and new
>   upstream changes are not necessary. The point is that COMMIT_MSG should
>   always be relative to what is in pkgsrc.
>
>   Unless you are a TNF member and intend to commit your own package later,
>   the committer will be different than the packager. It is appropriate to
>   add an additional section, typically before packaging changes, either
>   "Packaged in wip by Alyssa P. Hacker." or "Update prepared in wip by Ben
>   Bitdiddle".
>
>
> The point is to have the wip submitter do as much of the work as
> possible, so that people with pkgsrc write access who are helping move
> wip content to main can spend less time per package, and thus do more.



-- 
kikadf