You are not logged in.
Hey there,
currently, I'm about to add licensing information to my x32-edit PKGBUILD , but Behringer provides the EULA as pdf only.
When loking through /usr/share/licenses , I recognized that all the packages I installed provided either a plaintext- or a html-file. The packaging-standards just say, I should "copy the license to a file and include it"
Is it tolerated to just download & save the pdf, or should license-files be in a simpler format (which would need me to host the txt or html somewhere offside from the vendor)?
Thanks in advance.
Last edited by pheerai (2015-01-22 17:45:50)
Sincerely, pheerai
Send someone a pizza!
Web Git Github
Offline
I just found out that the poppler package has a pdftotext utility. Additionally, I tested it with the pdf file you pointed out: the final result looked nice.
I would convert it to text if I were packaging (you can add poppler to 'makedepends'),but I don't know if it is the recommended procedure.
Offline
pdftotext and pdftohtml both have a few problems with this pdf (first one messes up the chapter-enumeration, second one has char encoding problems).
Furthermore, I'm not a fan of adding 4.18 MB + deps of makedepends (even though poppler SHOULD be installed on almost any system, who doesn't need cups, loffice or texlive?)
My current hope is that I'll be able to convince Behringer of providing the EULA in txt or pdf themselves (I need to drop them a mail either way, their binary comes with an executable stack…).
Sincerely, pheerai
Send someone a pizza!
Web Git Github
Offline
Since you create the PKGBUILD, I'd suggest you manually create a text file and add that to the package. Maybe include a note that in case of differences/mistakes the pdf takes precedence.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Just use the pdf - if that is all upstream supplies, do the same.
Offline
Hm, OK.
I'll do that then.
Thanks everyone.
Sincerely, pheerai
Send someone a pizza!
Web Git Github
Offline