Mailing list archives : pcb-rnd

ID:5759
From:Erich Heinzle <a1...@gmail.com>
Date:Thu, 14 Jul 2022 22:27:21 +0930
Subject:Re: [pcb-rnd] file(1) support for our formats (was: file name policy
in-reply-to:5758 from rn...@igor2.repo.hu
--00000000000035ed0c05e3c372b9
Content-Type: text/plain; charset="UTF-8"
 
I can liase with the file(1) maintainer to add the necessary magic for
ringdove suite,  if there is a complete set of magic for the various
filetypes.
 
Regards,
 
Erich
 
On Thu, 14 Jul 2022 14:13 , <rnd2@igor2.repo.hu> wrote:
 
> 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
>
>
>
 
--00000000000035ed0c05e3c372b9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 
<div dir=3D"auto">I can liase with the file(1) maintainer to add the necess=
ary magic for ringdove suite,=C2=A0 if there is a complete set of magic for=
 the various filetypes.<div dir=3D"auto"><br></div><div dir=3D"auto">Regard=
s,=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Erich</div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On T=
hu, 14 Jul 2022 14:13 , &lt;<a href=3D"mailto:rnd2@igor2.repo.hu">rnd2@igor=
2.repo.hu</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, =
10 Jul 2022, <a href=3D"mailto:karl@aspodata.se" target=3D"_blank" rel=3D"n=
oreferrer">karl@aspodata.se</a> wrote:<br>
<br>
&gt;Unfortunately the program file just calls theese files<br>
&gt;for ascii text.<br>
<br>
&lt;snip&gt;<br>
<br>
&gt;So one way around this it to update your magicfile (mine is <br>
&gt;/usr/share/misc/magic.mgc). <br>
<br>
Last time I checked, file(1) had a centralized database option only, which =
<br>
is sad. It means we can&#39;t get a distro package simply extend the databa=
se <br>
by installing a few &quot;format plugin&quot; patterns in file&#39;s config=
 dir.<br>
<br>
We have a magic pattern for file(1) in trunk/doc/resources. (It&#39;s a bit=
 <br>
tricky: for example there&#39;s no guarantee the root node is the first lin=
e <br>
or starts at the beginning of a line.) On Debian (and probably many other <=
br>
distros) it&#39;s enough to append the content of this file to /etc/magic. =
So <br>
if you need it quick and local, it&#39;s rather easy to do already.<br>
<br>
If anyone is interested in doing the administration (registering wherever <=
br>
they need to, submitting the magic, communicating with the authors if <br>
necessary, etc) to get it included in the official central thing, I can <br=
>
revise and extend our magic file to ringdove, adding all our other file <br=
>
file types we have (for sch-rnd, camv-rnd, plus the tEDAx formats).<br>
<br>
The other popular infra is MIME, maintained by IANA. See <br>
<a href=3D"https://www.iana.org/assignments/media-types/media-types.xhtml" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://www.iana.org/assign=
ments/media-types/media-types.xhtml</a><br>
Same applies here: if anyone steps up to do the administration, I am happy =
<br>
to figure what input needs to be provided from the project side.<br>
<br>
<br>
Best regards,<br>
<br>
Igor2<br>
<br>
<br>
</blockquote></div>
 
--00000000000035ed0c05e3c372b9--
 

Reply subtree:
5759 Re: [pcb-rnd] file(1) support for our formats (was: file name policy from Erich Heinzle <a1...@gmail.com>