Re: TrueType/OpenType and anti-circumvention laws

2024-02-04 Thread Paul Wise
On Mon, 2024-01-15 at 06:05 -0500, P. J. McDermott wrote: > Paul Wise mentioned[8] on the fonts team list in 2021 a couple programs > ("embed"[9], a derivative "ttembed"[10], and "ttfpatch"[11]) that unset > the DRM/TPM bits, enabling full use of the fonts.  "embed" was written > by a font

Re: hard linking libboost copyright files

2024-02-04 Thread Walter Landry
Andreas Metzler writes: > On 2024-02-04 Muhammad Yaaseen wrote: >> The question is once we install the libboost .deb packages into a >> system, the copyright file for each libboost package is stored >> separately in /usr/shared/doc/packages folder. I'm think of >> hardlinking these copyright

Re: hard linking libboost copyright files

2024-02-04 Thread Andreas Metzler
On 2024-02-04 Andreas Metzler wrote: [...] > The canonical solution would be to add libboost-commonx.xx containing > what is currently found in /usr/share/doc/libboost-foox.xx and symlink > the whole directory. You'll probably need to make libboost-commonx.xx > arch all to be binNMU compatible.

Re: hard linking libboost copyright files

2024-02-04 Thread Andreas Metzler
On 2024-02-04 Muhammad Yaaseen wrote: > The question is once we install the libboost .deb packages into a > system, the copyright file for each libboost package is stored > separately in /usr/shared/doc/packages folder. I'm think of > hardlinking these copyright files so that we same some memory.

RE: hard linking libboost copyright files

2024-02-04 Thread Muhammad Yaaseen
Hi, The question is once we install the libboost .deb packages into a system, the copyright file for each libboost package is stored separately in /usr/shared/doc/packages folder. These copyright files are all the same. I'm think of hardlinking these copyright files so that we same some

Re: hard linking libboost copyright files

2024-02-04 Thread Steve Langasek
On Sun, Feb 04, 2024 at 10:50:43AM +, Muhammad Yaaseen wrote: > The question is once we install the libboost .deb packages into a system, > the copyright file for each libboost package is stored separately in > /usr/shared/doc/packages folder. I'm think of hardlinking these copyright > files

RE: hard linking libboost copyright files

2024-02-04 Thread Muhammad Yaaseen
Hi Steve, The question is once we install the libboost .deb packages into a system, the copyright file for each libboost package is stored separately in /usr/shared/doc/packages folder. I'm think of hardlinking these copyright files so that we same some memory. Is this legally allowed.

Re: hard linking libboost copyright files

2024-02-04 Thread Steve Langasek
On Sun, Feb 04, 2024 at 05:38:57AM +, Muhammad Yaaseen wrote: > we see that the copyright for libboost debian packages are 2MB each and > are all the same. as per > https://www.debian.org/doc/debian-policy/ch-docs.html section >

hard linking libboost copyright files

2024-02-04 Thread Muhammad Yaaseen
Hi, we see that the copyright for libboost debian packages are 2MB each and are all the same. as per https://www.debian.org/doc/debian-policy/ch-docs.html section 12.5 we are not allowed to create symbolic links. the doubt