On 2021-05-22 09:15, Jason Pyeron wrote:
Which is more correct – the https://cygwin.com/packaging-contributors-guide.html
or cygport generated email?
The description is good, but the suggested content is outdated, as the mailing
list
software and instructions have changed since that was written, and adding
outdated,
inaccurate, no longer working cygwin-announce unsubscribe info, with references
to
email headers, when the email content is also forwarded to the cygwin list,
intended
for general users, which adds its own unsubscribe info, and is a better current
unsubscribe link.
For an example of the confusing and outdated info see e.g.:
https://cygwin.org/pipermail/cygwin/2021-May/248413.html
[Not picking on you Achim, but the content is outdated as mentioned above, and
inappropriate on the cygwin list, and with my user hat on, should be stripped
like any
other signature from "^-- $", on forwarding from the cygwin-announce to cygwin
lists.]
The cygport content is better, but as the description on that page says, you
could add
info about the upstream project and/or packages, where to get more project and
change
info, and a summary of the changes since the last Cygwin stable production
release.
What I do is:
- take the previous notice (download from cygwin-announce mailing list if
adopted),
- copy and tweak and update versions,
- identify the DOCS content with the best summary level change info e.g.
ChangeLog, CHANGES, KNOWN_BUGS, NEWS, etc.,
- append the change info, reformat, and tweak more tersely,
- mention paths or links to installed and online versions, with more details,
then
- after starting "cygport ... announce",
- in your editor append your project, package, and release notice,
- edit in with the announce content and tweak,
- save for announce to send,
- also save in the cygport project/package directory for your reference, and
- exit to send.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
