Re: [directory-discuss] guix tags that could be automatically extracted

[ng0 <ng0@infotropique.org>]

[-- Attachment #1: Type: text/plain, Size: 3919 bytes --]

Tobias Geerinckx-Rice transcribed 4.2K bytes:
> Quiliro,
> 
> [Not-cross-posting this to guix-devel.]
> 
> On 16/07/17 03:35, Quiliro Ordonez Baca wrote:
> > Using:
> > 'guix package --show=emacs'
> > for example, it is possible to get a lot of information from a
> > package. It could be used to include in the Directory. Or it could be
> > the other way around: guix could extract information from the Directory
> > in order to define packages.
> 
> This might make an interesting option to ‘guix import’, if only to give
> packagers something to start with. I'm not sure if it would result in
> enough useful hits to make it worthwhile. On the other hand, there's
> only one way to find out.

What I expressed last night:

I don't want any additions to the connections made without the consent
of people using guix.
What exactly does this mean?
Everything should be within Guix. The default should be to *not* call
some mediawiki for more information. If we even have the option to query
this mediawiki and the information doesn't have to be present in guix
like translations, I want it to be optional and you have to opt-in to
(receiving) these (informations).

Please discuss this either on guix-devel or on the other list, but don't
CC me into one of the famous gnu.org cross-posting discussions. Thanks
for your consideration.

> 
> I'll paste what I wrote in #guix, though:
> 
>   “I wonder what the copyright situation would be for that. If the
>    descriptions are copyrightable, the individual contributors retain
>    their copyright. On the other hand, the vast majority of
>    descriptions are straight from the home page, Wikipedia, or both.”
> 
> I'm not a lawyer nor do I play one on TV, but assume this would apply in
> both directions.
> 
> > Although it would be easier the former way.
> 
> From my limited experience with MediaWiki, I'd bet the opposite. I know
> there's a machine-readable dump of the Directory database somewhere,
> that's updated at least semi-regularly. I don't know if it's
> comprehensive. The directory-discuss archives might.
> 
> Kind regards,
> 
> T G-R
> 
> > The output of the above command is:
> > name: emacs
> > version: 25.2
> > outputs: out
> > systems: x86_64-linux i686-linux armhf-linux aarch64-linux mips64el-linux
> > dependencies: acl-2.2.52 alsa-lib-1.1.3 dbus-1.10.18 giflib-5.1.4
> > + gnutls-3.5.9 gtk+-3.22.15 imagemagick-6.9.8-10 libice-1.0.9 libjpeg-8d
> > + libotf-0.9.13 libpng-1.6.28 librsvg-2.40.16 libsm-1.2.2 libtiff-4.0.7
> > + libx11-1.6.5 libxft-2.3.2 libxml2-2.9.4 libxpm-3.5.12 m17n-lib-1.7.0
> > + ncurses-6.0 pkg-config-0.29.1 texinfo-6.3 zlib-1.2.11
> > location: gnu/packages/emacs.scm:102:2
> > homepage: https://www.gnu.org/software/emacs/
> > license: GPL 3+
> > synopsis: The extensible, customizable, self-documenting text editor  
> > description: GNU Emacs is an extensible and highly customizable text
> > + editor.  It is based on an Emacs Lisp interpreter with extensions for text
> > + editing.  Emacs has been extended in essentially all areas of computing,
> > + giving rise to a vast array of packages supporting, e.g., email, IRC and
> > + XMPP messaging, spreadsheets, remote server editing, and much more.  Emacs
> > + includes extensive documentation on all aspects of the system, from basic
> > + editing to writing large Lisp programs.  It has full Unicode support for
> > + nearly all human languages.
> > 
> > There are many ways to select each tag and filter by each tag. So it
> > could be useful for the Directory.
> > 
> > I am a newbie with Guix. So I bet some Guix hackers on this list could
> > supplement this idea. On the other hand, I learn quickly!
> 




-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]