Re: [ITP] openh264 (2.3.1)
On Tue, 21 Feb 2023 14:11:46 +
Jon Turney wrote:
> On 20/02/2023 08:55, Takashi Yano via Cygwin-apps wrote:
> > On Sun, 19 Feb 2023 15:37:47 +
> > Jon Turney wrote:
> [...]>> * I don't think you should need:
> >>
> >>> # Install postinstall/preremove scripts
> >>> mkdir -p ${D}/etc/postinstall ${D}/etc/preremove
> >>> cp ${C}/lib${NAME}.postinstall ${D}/etc/postinstall/lib${NAME}.sh
> >>> cp ${C}/lib${NAME}.preremove ${D}/etc/preremove/lib${NAME}.sh
> >>>
> >>
> >> This should happen automatically if the files are in $C (and you can
> >> list them in CYGWIN_FILES or make them with cygwin.patch file to put
> >> them there)
> >
> > That's what I understood from
> > https://cygwin.github.io/cygport/masterindex.html,
> > however, actually libopenh264.{postinstall,preremove} are
> > not installed during install process by cygport 0.36.0
> > even though openh264-2.3.1-1.cygwin.patch exists.
> >
> > Could you please give me a hint how I can make it work?
>
> Aha! This is a bug in cygport.
>
> (There's some code which skips over doing this for the first item in
> PKG_NAMES, assuming that is always the same as PN, which has already
> been done)
>
> Thanks for drawing that to my attention. I'll look into fixing it, but
> for the moment it seems you can workaround the bug by ensuring that the
> package with premove/postinstall scripts isn't first in that list, i.e.:
>
> - PKG_NAMES="libopenh264 libopenh264-headers"
> + PKG_NAMES="libopenh264-headers libopenh264"
Thanks! It works.
I updated the cygport file and cygwin.patch.
--
Takashi Yano
NAME="openh264"
VERSION=2.3.1
RELEASE=1
CATEGORY="Video"
SUMMARY="H.264 codec library by Cisco"
DESCRIPTION="OpenH264 is a codec library which supports H.264 encoding and
decoding. It is suitable for use in real time applications such as WebRTC. The
binary library (runtime) itself will be downloaded from
http://ciscobinary.openh264.org/;
HOMEPAGE="https://www.openh264.org/;
LICENSE="BSD-2-Clause"
ARCH="noarch" # This is noarch because it's just header files and shell scrpits.
SRC_URI="${NAME}-headers-${VERSION}.tar.xz"
# Make dummy source file for prep if the cleaned one is not exist.
if [ ! -f ${SRC_URI} ]
then
mkdir -p ${NAME}-${VERSION}
tar acf ${SRC_URI} ${NAME}-${VERSION}
rm -rf ${NAME}-${VERSION}
fi
CYGPORT_USE_UNSTABLE_API=1
src_unpack_hook() {
if [ $(tar tvf ../../../${SRC_URI} | wc -l) -eq 1 ] # Source file is
dummy
then
NV=${NAME}-${VERSION}
pushd ..
# Download original source file.
wget -q
https://github.com/cisco/openh264/archive/refs/tags/v${VERSION}.tar.gz -O - |
tar xzf -
# Make source tarball file which has only necessary header
files.
tar acf ../../${NAME}-headers-${VERSION}.tar.xz
${NV}/codec/api/wels/*.h
# Update source directory.
rm -rf ${NV}
tar xf ../../${NAME}-headers-${VERSION}.tar.xz
popd
fi
}
PKG_NAMES="libopenh264-headers libopenh264"
libopenh264_CATEGORY="Video Libs"
libopenh264_CONTENTS="etc/ usr/share/"
libopenh264_REQUIRES="wget bzip2"
libopenh264_SUMMARY="H.264 codec library runtime by Cisco"
libopenh264_headers_CATEGORY="Video Devel"
libopenh264_headers_CONTENTS="usr/include"
libopenh264_headers_SUMMARY="H.264 codec library headers"
src_compile() {
:
}
src_install() {
mkdir -p ${D}/usr/include
ln -fs ${S}/codec/api/wels ${D}/usr/include/.
# Get license file
mkdir -p ${D}/usr/share/doc/lib${NAME}
if ! wget -q http://www.openh264.org/BINARY_LICENSE.txt -O - >
${D}/usr/share/doc/lib${NAME}/BINARY_LICENSE.txt
then
echo "Need internet access!!!"
exit 1
fi
mkdir -p ${D}/etc/lib${NAME}
# Make sha256 hash
wget -q
http://ciscobinary.openh264.org/${NAME}-${VERSION}-win64.dll.bz2 -O - | bunzip2
| sha256sum | sed "s/-$/${NAME}-${VERSION}-win64.tmp/" >
${D}/etc/lib${NAME}/${NAME}-${VERSION}-win64.dll.sha256
wget -q
http://ciscobinary.openh264.org/${NAME}-${VERSION}-win32.dll.bz2 -O - | bunzip2
| sha256sum | sed "s/-$/${NAME}-${VERSION}-win32.tmp/" >
${D}/etc/lib${NAME}/${NAME}-${VERSION}-win32.dll.sha256
# Make version text
echo ${VERSION} > ${D}/etc/lib${NAME}/version.txt
}
--- origsrc/openh264-2.3.1/CYGWIN-PATCHES/libopenh264.postinstall
1970-01-01 09:00:00.0 +0900
+++ src/openh264-2.3.1/CYGWIN-PATCHES/libopenh264.postinstall 2023-02-17
12:36:27.633701700 +0900
@@ -0,0 +1,18 @@
+if [ $(uname -m) = "x86_64" ]
+then
+ POSTFIX="win64"
+else
+ POSTFIX="win32"
+fi
+VERSION=$(cat /etc/libopenh264/version.txt)
+cd /tmp
+wget -q http://ciscobinary.openh264.org/openh264-${VERSION}-${POSTFIX}.dll.bz2
-O - | bunzip2 > openh264-${VERSION}-${POSTFIX}.tmp
+if sha256sum --status -c
Updated: ed-1.19-1
New version 1.19-1 of ed is available in the Cygwin distribution: CHANGES It is a upstream bugfix release. DESCRIPTION GNU ed is a line-oriented text editor. It is used to create, display, modify and otherwise manipulate text files, both interactively and via shell scripts. A restricted version of ed, red, can only edit files in the current directory and cannot execute shell commands. Ed is the "standard" text editor in the sense that it is the original editor for Unix, and thus widely available. HOMEPAGE http://www.gnu.org/software/ed/ Marco Atzeri If you have questions or comments, please send them to the cygwin mailing list at: cygwin (at) cygwin (dot) com .
[ANNOUNCEMENT] Updated: ed-1.19-1
New version 1.19-1 of ed is available in the Cygwin distribution: CHANGES It is a upstream bugfix release. DESCRIPTION GNU ed is a line-oriented text editor. It is used to create, display, modify and otherwise manipulate text files, both interactively and via shell scripts. A restricted version of ed, red, can only edit files in the current directory and cannot execute shell commands. Ed is the "standard" text editor in the sense that it is the original editor for Unix, and thus widely available. HOMEPAGE http://www.gnu.org/software/ed/ Marco Atzeri If you have questions or comments, please send them to the cygwin mailing list at: cygwin (at) cygwin (dot) com . -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: autoconf-archive-2023.02.20-1
Autoconf Archive has been updated to the latest upstream release 2023.02.20 on Cygwin. The GNU Autoconf Archive is a collection of more than 450 macros for GNU Autoconf that have been contributed as free software by friendly supporters of the cause from all over the Internet. -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Updated: autoconf-archive-2023.02.20-1
Autoconf Archive has been updated to the latest upstream release 2023.02.20 on Cygwin. The GNU Autoconf Archive is a collection of more than 450 macros for GNU Autoconf that have been contributed as free software by friendly supporters of the cause from all over the Internet. -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
[ANNOUNCEMENT] Updated: openssl 1.1.1t-1, mingw64-{i686, x86_64}-openssl-1.1.1t-0.2 (security)
The following packages have been uploaded to the Cygwin distribution. This release updates to the latest upstream security patch release and continues to use the Fedora patches from an earlier release (Fedora has already switched to openssl 3.x). * openssl-1.1.1t-1 * openssl-perl-1.1.1t-1 * libssl1.1-1.1.1t-1 * libssl-devel-1.1.1t-1 The following MinGW64 test packages are made available: * mingw64-i686-openssl-1.1.1t-0.2 * mingw64-x86_64-openssl-1.1.1t-0.2 The OpenSSL toolkit provides support for secure communications between machines. OpenSSL includes a certificate management tool and shared libraries which provide various cryptographic algorithms and protocols. -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Updated: openssl 1.1.1t-1, mingw64-{i686,x86_64}-openssl-1.1.1t-0.2 (security)
The following packages have been uploaded to the Cygwin distribution. This release updates to the latest upstream security patch release and continues to use the Fedora patches from an earlier release (Fedora has already switched to openssl 3.x). * openssl-1.1.1t-1 * openssl-perl-1.1.1t-1 * libssl1.1-1.1.1t-1 * libssl-devel-1.1.1t-1 The following MinGW64 test packages are made available: * mingw64-i686-openssl-1.1.1t-0.2 * mingw64-x86_64-openssl-1.1.1t-0.2 The OpenSSL toolkit provides support for secure communications between machines. OpenSSL includes a certificate management tool and shared libraries which provide various cryptographic algorithms and protocols. -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Re: OSError: Unsupported platform 'CYGWIN_NT-10.0-19044'
On 2/22/2023 7:03 AM, Jose Isaias Cabrera via Cygwin wrote: On February 21, 2023 2:52 AM, Csaba Raduly expressed: Because you're not on Windows. You're on Cygwin, which acts as a POSIX (Unix-like) system. Wow! Thanks for that deep thought. :-) I knew that. :-) I have been using Cygwin since 1999 (sometimes more than others). I just thought that by now, Windows would have started playing nicer and had made enough changes to be friendlier to POSIX. Long story, but I need to use Cygwin for this. Thanks, though. Sorry - hard to know whether one is dealing with a "newbie" or not. EM -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
RE: OSError: Unsupported platform 'CYGWIN_NT-10.0-19044'
On February 21, 2023 2:52 AM, Csaba Raduly expressed: > Because you're not on Windows. You're on Cygwin, which acts as a POSIX > (Unix-like) system. Wow! Thanks for that deep thought. :-) I knew that. :-) I have been using Cygwin since 1999 (sometimes more than others). I just thought that by now, Windows would have started playing nicer and had made enough changes to be friendlier to POSIX. Long story, but I need to use Cygwin for this. Thanks, though. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] gdb 12.1-1 (TEST)
On 19/05/2022 17:05, Jon Turney wrote: The following package has been updated in the Cygwin distribution: * gdb-12.1-1 The GNU debugger allows you to debug programs written in C, C++, and other languages, by executing them in a controlled fashion and printing their data. This is an update to the latest upstream version: https://sourceware.org/pipermail/gdb-announce/2022/000132.html See the /usr/share/doc/gdb/NEWS file for a list of user-visible changes. This package has (belatedly) been promoted from test to current. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] gdb 13.1-1 (TEST)
The following package has been updated in the Cygwin distribution: * gdb-13.1-1 The GNU debugger allows you to debug programs written in C, C++, and other languages, by executing them in a controlled fashion and printing their data. This is an update to the latest upstream version: https://sourceware.org/pipermail/gdb-announce/2023/000134.html See the /usr/share/doc/gdb/NEWS file for a list of user-visible changes. Of particular interest: * The 'disable-randomization' setting now works on Windows versions which support disabling ASLR for a spawned process. If supported, it's on by default. * GDB can now show thread names set with SetThreadDescription() (which is used by Cygwin's implementation of pthread_setname_np(), the equivalent UNIX API) In addition, it contains the following patches carried forward from the previous Cygwin package: * Teach the demangler to deal with '@'-decorated __stdcall functions * (experimental) Teach gdb how to unwind frames for the Cygwin signal delivery wrapper functions _sigbe and sigdelayed * Fix a memory leak which would occur in the case when the result of realpath() is greater than or equal to SO_NAME_MAX_PATH_SIZE (Corinna Vinschen) * Simplify and improve handling of inferior context after a Cygwin signal * Use cygwin pgid if inferior is a cygwin process (Takashi Yano) -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
gdb 13.1-1 (TEST)
The following package has been updated in the Cygwin distribution: * gdb-13.1-1 The GNU debugger allows you to debug programs written in C, C++, and other languages, by executing them in a controlled fashion and printing their data. This is an update to the latest upstream version: https://sourceware.org/pipermail/gdb-announce/2023/000134.html See the /usr/share/doc/gdb/NEWS file for a list of user-visible changes. Of particular interest: * The 'disable-randomization' setting now works on Windows versions which support disabling ASLR for a spawned process. If supported, it's on by default. * GDB can now show thread names set with SetThreadDescription() (which is used by Cygwin's implementation of pthread_setname_np(), the equivalent UNIX API) In addition, it contains the following patches carried forward from the previous Cygwin package: * Teach the demangler to deal with '@'-decorated __stdcall functions * (experimental) Teach gdb how to unwind frames for the Cygwin signal delivery wrapper functions _sigbe and sigdelayed * Fix a memory leak which would occur in the case when the result of realpath() is greater than or equal to SO_NAME_MAX_PATH_SIZE (Corinna Vinschen) * Simplify and improve handling of inferior context after a Cygwin signal * Use cygwin pgid if inferior is a cygwin process (Takashi Yano)
Re: A query about latest update to "make"
On 21.02.2023 14:49, Fergus Daly via Cygwin wrote: I update my local Cygwin using setup-x86_64.exe. The latest setup.ini file includes the lines setup-timestamp: 1676945925 setup-version: 2.924 @ make version: 4.4-1 [prev] version: 4.3-1 [test] version: 4.4.0.91-1 I definitely do not use the switch -t (for test versions); and yet, following today's update, my /etc/setup/installed.db file includes the lines INSTALLED.DB 3 make make-4.4.0.91-1.tar.bz2 0 Not at all sure why not v.4.4-1? Hi Fergus, my fault I uploadd by mistake 4.4.0.90-2 without marking it as test. I replaced it later with the test 4.4.0.91-1 If you installed the 4.4.0.90-2, setup will push the 4.4.0.91-1 as next version Regards Marco -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: ACL
On 2023-02-21 06:51, Thomas Wolff via Cygwin-apps wrote: Am 21.02.2023 um 14:10 schrieb Jonathan Chapman-Moore via Cygwin-apps: ML cygwin-apps is for packagers issues, not general distro or features discussion, moving to cygwin for followup. I was wondering when ACL was going to be added to Cygwin? It's long been available, see /bin/[gs]etfacl Cygwin has always had to deal with Windows ACLs and ACEs, mostly behind the scenes following a Solaris model until 1.7, moving towards POSIX in 2.4, then more comprehensively and overtly from 2.5, to provide RFC and POSIX compliance, reducing Solaris influence, and better NIS, NFS, and Samba support. See referenced and earlier: https://cygwin.com/cygwin-ug-net/ov-new.html#ov-new2.5 https://cygwin.com/cygwin-ug-net/ntsec.html -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Copyright outdated? in Cygwin/X FAQ 12.6 and not addressed in Cygwin FAQ 7.1 link
On 2023-02-21 02:12, Corinna Vinschen wrote: On Feb 20 13:20, Brian Inglis wrote: Hi folks, [Addressing to patches as that's where we'll fix it, and not a general issue.] Noticed that: https://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-copyright-cygwin "12.6. Who holds the copyright on the Cygwin source code? Red Hat owns the copyright on the Cygwin source code. Red Hat requires that copyright be assigned to Red Hat for non-trivial changes to Cygwin. You must fill out a copyright transfer form if you are going to contribute substantial changes to Cygwin." Has that not been assigned to the project? And also: https://cygwin.com/faq/faq.html#faq.what.copyright "7.1. What are the copyrights? 7.1. What are the copyrights? Please see https://cygwin.com/licensing.html for more information about Cygwin copyright and licensing." -> "Cygwin™ Linking Exception As a special exception, the copyright holders of the Cygwin library" Is that the project? Yes, that's the Cygwin project, not the distro as a whole. All packages in the distro have their own license. THe above is strictly only about the Cygwin project license as defined by ... [...] Or does it belong to the authors individually and/or the project or the https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/CYGWIN_LICENSE After Red Hat stopped selling the Cygwin buyout license, Red Hat changed the license of the DLL to "GPLv3+ w/ linking exception" and handed the copyright over to the community, so the copyright holders are the individual contributors, most of which are mentioned in https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/CONTRIBUTORS The former buyout licenses had a pretty long lifetime, so it was necessary from a legal perspective, that contributors passed over the code under a BSD-2-clause license as long as the buyout licenses were active. This time has passed in the meantime, so we don't really need the CONTRIBUTORS file anymore. "Cygwin authors" collectively? The project doesn't "belong" anybody anymore. The project has copyright holders. Those are the developers contributing code to the project collectively. Thanks Corinna, That makes sense and I will see how I can tweak the FAQs to reflect the current status, likely X 12.6 refers to Cygwin 7.1, which makes that explicit statement. I will make and send patches. It is still worth getting licence agreements and updating and maintaining the CONTRIBUTORS file to acknowledge the copyright holders, and give the project a basis for contact in case there is ever any need to modify licences, or any other reason to contact copyright holders. Without that list, the project can not contact copyright holders, so terms or licences can never change, if the current sources or licence(s) ever have problem(s) for any reason, so the project could have to reconstituted on some other basis, or else abandoned! -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry
Re: [ITP] openh264 (2.3.1)
On 20/02/2023 08:55, Takashi Yano via Cygwin-apps wrote:
On Sun, 19 Feb 2023 15:37:47 +
Jon Turney wrote:
[...]>> * I don't think you should need:
# Install postinstall/preremove scripts
mkdir -p ${D}/etc/postinstall ${D}/etc/preremove
cp ${C}/lib${NAME}.postinstall ${D}/etc/postinstall/lib${NAME}.sh
cp ${C}/lib${NAME}.preremove ${D}/etc/preremove/lib${NAME}.sh
This should happen automatically if the files are in $C (and you can
list them in CYGWIN_FILES or make them with cygwin.patch file to put
them there)
That's what I understood from
https://cygwin.github.io/cygport/masterindex.html,
however, actually libopenh264.{postinstall,preremove} are
not installed during install process by cygport 0.36.0
even though openh264-2.3.1-1.cygwin.patch exists.
Could you please give me a hint how I can make it work?
Aha! This is a bug in cygport.
(There's some code which skips over doing this for the first item in
PKG_NAMES, assuming that is always the same as PN, which has already
been done)
Thanks for drawing that to my attention. I'll look into fixing it, but
for the moment it seems you can workaround the bug by ensuring that the
package with premove/postinstall scripts isn't first in that list, i.e.:
- PKG_NAMES="libopenh264 libopenh264-headers"
+ PKG_NAMES="libopenh264-headers libopenh264"
Re: ACL
Am 21.02.2023 um 14:10 schrieb Jonathan Chapman-Moore via Cygwin-apps: Hi, I was wondering when ACL was going to be added to Cygwin? It's long been available, see /bin/[gs]etfacl
A query about latest update to "make"
I update my local Cygwin using setup-x86_64.exe. The latest setup.ini file includes the lines setup-timestamp: 1676945925 setup-version: 2.924 @ make version: 4.4-1 [prev] version: 4.3-1 [test] version: 4.4.0.91-1 I definitely do not use the switch -t (for test versions); and yet, following today's update, my /etc/setup/installed.db file includes the lines INSTALLED.DB 3 make make-4.4.0.91-1.tar.bz2 0 Not at all sure why not v.4.4-1? -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
ACL
Hi, I was wondering when ACL was going to be added to Cygwin? http://savannah.nongnu.org/projects/acl Thanks, Jonathan Moore
Re: Copyright outdated? in Cygwin/X FAQ 12.6 and not addressed in Cygwin FAQ 7.1 link
On Feb 20 13:20, Brian Inglis wrote: > Hi folks, > [Addressing to patches as that's where we'll fix it, and not a general issue.] > > Noticed that: > > https://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-copyright-cygwin > > "12.6. Who holds the copyright on the Cygwin source code? > > Red Hat owns the copyright on the Cygwin source code. Red Hat requires that > copyright be assigned to Red Hat for non-trivial changes to Cygwin. You must > fill out a copyright transfer form if you are going to contribute > substantial changes to Cygwin." > > Has that not been assigned to the project? > > And also: > > https://cygwin.com/faq/faq.html#faq.what.copyright > > "7.1. What are the copyrights? > 7.1. > What are the copyrights? > Please see https://cygwin.com/licensing.html for more information about > Cygwin copyright and licensing." > > -> > > "Cygwin™ Linking Exception > As a special exception, the copyright holders of the Cygwin library" > > Is that the project? Yes, that's the Cygwin project, not the distro as a whole. All packages in the distro have their own license. THe above is strictly only about the Cygwin project license as defined by ... > [...] > Or does it belong to the authors individually and/or the project or the https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/CYGWIN_LICENSE After Red Hat stopped selling the Cygwin buyout license, Red Hat changed the license of the DLL to "GPLv3+ w/ linking exception" and handed the copyright over to the community, so the copyright holders are the individual contributors, most of which are mentioned in https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/CONTRIBUTORS The former buyout licenses had a pretty long lifetime, so it was necessary from a legal perspective, that contributors passed over the code under a BSD-2-clause license as long as the buyout licenses were active. This time has passed in the meantime, so we don't really need the CONTRIBUTORS file anymore. > "Cygwin authors" collectively? The project doesn't "belong" anybody anymore. The project has copyright holders. Those are the developers contributing code to the project collectively. Corinna
