From: ludo@gnu.org (Ludovic Courtès)
To: Dima Ursu <dima@tehnoetic.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: All source code for GuixSD system
Date: Fri, 19 May 2017 17:39:32 +0200 [thread overview]
Message-ID: <87d1b4etzf.fsf@gnu.org> (raw)
In-Reply-To: <cb710463-0adb-9dab-933f-9b3f746bc229@tehnoetic.com> (Dima Ursu's message of "Fri, 19 May 2017 14:18:57 +0300")
Hello Dima,
(+Cc: help-guix)
Dima Ursu <dima@tehnoetic.com> skribis:
> On 05/17/2017 12:03 AM, Ludovic Courtès wrote:
[...]
>> If you run:
>>
>> guix gc -R $(readlink -f /run/current-system)
>>
>> on a GuixSD system, that’ll list all the “things” the system itself
>> references. Some of these things are configuration files, but many
>> others are the actual packages.
>
> Thanks, Ludo, that's what I was looking for!
>
>> A rough approach would be to run something along these lines:
>>
>> guix build --sources=transitive \
>> $(guix gc -R $(readlink -f /run/current-system) | \
>> grep -e '-[0-9.]\+$' | \
>> sed -'es,/gnu/store/.\{32\}-\(.*\)-\([0-9.]\+\)$,\1@\2,g')
>
> I've run this in several stages, and it seems that grep -e '-[0-9.]\+$'
> is a bit too aggressive - some packages that I think are valid are
> excluded, like:
> tz-data
> mutter
> libjpeg-9b
> libcdio-paranoia
> xf86-video-intel
>
> They either have some letters at the end, or not have a version at all.
> I wonder if the "--sources=transitive" would take care of them and pull
> them anyway, but there's no obvious way to be sure of that.
Yeah, I guess you could fine-tune the regexp as a first step.
> There are some .scm files, which I assume are already in the source
> version, but correct me if I'm wrong.
Yes, these are just copied from Guix proper to /gnu/store.
> Some of the reported packages confuse me, like boot, fstab, profile,
> raw-initrd, system - and they won't even build - guix just reports them
> as "unknown package". Should I bother at all with them?
These are non-package byproducts used by the system (everything ‘guix
system’ and other tools build goes to /gnu/store, including
configuration files, the initrd, and so on.) It’s safe to ignore them.
HTH,
Ludo’.
prev parent reply other threads:[~2017-05-19 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 12:11 All source code for GuixSD system Dima Ursu
2017-05-16 9:50 ` Efraim Flashner
2017-05-16 19:46 ` Ludovic Courtès
2017-05-16 20:06 ` Tiberiu
2017-05-16 20:11 ` Fox
2017-05-16 21:03 ` Ludovic Courtès
[not found] ` <cb710463-0adb-9dab-933f-9b3f746bc229@tehnoetic.com>
2017-05-19 15:39 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1b4etzf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dima@tehnoetic.com \
--cc=help-guix@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.