From: swedebugia <swedebugia@riseup.net>
To: guix-devel@gnu.org
Subject: Annotated guix source folder tree
Date: Wed, 7 Nov 2018 18:44:08 +0100 [thread overview]
Message-ID: <f0a71fee-fe46-ed0c-c7f4-96755fb91e3e@riseup.net> (raw)
Hi
I exported the tree and would like an annotated version to be added to
the manual.
Would you agree that this is a good idea?
I started the annotation below for the directories I know about. :)
We could have two versions: 1 for new users with a stripped down tree
and a full version for hackers/tinkerers.
What do you think?
$ tree -d
.
├── build-aux
│ ├── cuirass
│ └── hydra
├── doc ; Documentation
│ └── images
├── etc
│ ├── completion ; Completion syntax files for
different shells
│ │ ├── bash
│ │ ├── fish
│ │ └── zsh
│ ├── git
│ ├── snippets
│ │ ├── scheme-mode
│ │ └── text-mode
│ └── substitutes
├── gnu ; Base of the modules that make up Guix
│ ├── bootloader
│ ├── build
│ ├── packages ; The packages roughly categorized in
files
│ │ ├── aux-files
│ │ │ ├── emacs
│ │ │ └── linux-libre
│ │ ├── bootstrap ; Bootstrap file for running guix on
different CPU architectures
│ │ │ ├── aarch64-linux
│ │ │ ├── armhf-linux
│ │ │ ├── i686-linux
│ │ │ ├── mips64el-linux
│ │ │ └── x86_64-linux
│ │ └── patches ; Patches used in package-records to
make software build reproducibly
│ ├── services ; Service definitions for GuixSD
│ ├── system
│ │ └── examples ; Example GuixSD operating system
definitions
│ └── tests ; Tests to ensure everything works
as expected
├── guix
│ ├── build ; Build related code running isolated
on the daemon side.
│ ├── build-system ; Build systems to handle packages
written in different programming languages
│ ├── import ; Helper code to import packages from
other package collections
│ ├── scripts
│ │ ├── container
│ │ ├── import
│ │ └── system ; Guix commands related to system
manipulation
│ ├── store ; Code related to the monadic store
managed by the daemon
│ └── tests ; Tests to ensure everything works as
expected
├── m4
├── nix ; Build daemon written in C++ yet to be
ported to Guile Scheme
│ ├── boost
│ │ └── format
│ ├── libstore
│ ├── libutil
│ ├── nix-daemon
│ └── scripts
├── po ; Translation documents
│ ├── doc
│ ├── guix
│ └── packages
├── scripts
└── tests ; Tests to ensure everything works
as expected
--
Cheers
Swedebugia
next reply other threads:[~2018-11-07 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 17:44 swedebugia [this message]
2018-11-07 17:53 ` Annotated guix source folder tree Pierre Neidhardt
2018-11-08 9:32 ` swedebugia
2018-11-14 16:32 ` Oleg Pykhalov
2018-11-14 18:38 ` swedebugia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f0a71fee-fe46-ed0c-c7f4-96755fb91e3e@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).