| ID: | 5758 |
| From: | rn...@igor2.repo.hu |
| Date: | Thu, 14 Jul 2022 06:30:50 +0200 (CEST) |
| Subject: | [pcb-rnd] file(1) support for our formats (was: file name policy change proposal) |
| in-reply-to: | 5736 from ka...@aspodata.se |
| replies: | 5759 from Erich Heinzle <a1...@gmail.com> |
On Sun, 10 Jul 2022, karl@aspodata.se wrote: >Unfortunately the program file just calls theese files >for ascii text. <snip> >So one way around this it to update your magicfile (mine is >/usr/share/misc/magic.mgc). Last time I checked, file(1) had a centralized database option only, which is sad. It means we can't get a distro package simply extend the database by installing a few "format plugin" patterns in file's config dir. We have a magic pattern for file(1) in trunk/doc/resources. (It's a bit tricky: for example there's no guarantee the root node is the first line or starts at the beginning of a line.) On Debian (and probably many other distros) it's enough to append the content of this file to /etc/magic. So if you need it quick and local, it's rather easy to do already. If anyone is interested in doing the administration (registering wherever they need to, submitting the magic, communicating with the authors if necessary, etc) to get it included in the official central thing, I can revise and extend our magic file to ringdove, adding all our other file file types we have (for sch-rnd, camv-rnd, plus the tEDAx formats). The other popular infra is MIME, maintained by IANA. See https://www.iana.org/assignments/media-types/media-types.xhtml Same applies here: if anyone steps up to do the administration, I am happy to figure what input needs to be provided from the project side. Best regards, Igor2
Reply subtree:
5758 [pcb-rnd] file(1) support for our formats (was: file name policy change proposal) from rn...@igor2.repo.hu
5759 Re: [pcb-rnd] file(1) support for our formats (was: file name policy from Erich Heinzle <a1...@gmail.com>