From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: guix-devel@gnu.org
Subject: dmd: make user-mode easier to use.
Date: Mon, 3 Feb 2014 18:37:43 +0100 [thread overview]
Message-ID: <1391449065-19063-1-git-send-email-alex.sassmannshausen@gmail.com> (raw)
Hello,
This patch series allows dmd to work out of the box in 'user-mode'
after installation. To achieve this it ensures all dmd related files
are stored in ~/.dmd.d/ when run in user-mode, and it creates a
bare-bones configuration file for the user to start building upon if
no configuration file exists yet.
I decided to implement the above minimising any changes to the actual
logic of existing dmd. The result is a slight mixing up of side-effect
folder/file creation and side-effect free checks.
The alternative would have been to separate the folder creation from
the procedures carrying out the checks for the existence of the
configuration folder and files.
I wasn't sure whether it was better to minimise the changes in the
patches or better to 'just do the right thing', even if it entails
larger and more complex patches. Let me know your thoughts if you
think I should have gone the other way.
Best wishes,
Alex
next reply other threads:[~2014-02-03 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 17:37 Alex Sassmannshausen [this message]
2014-02-03 17:37 ` =?y?q?=5BPATCH=201/2=5D=20dmd=3A=20Use=20=7E/=2Edmd=2Ed/=20by=20default=20when=20not=20run=20as=20root=2E?= Alex Sassmannshausen
2014-02-04 20:34 ` [PATCH 1/2] dmd: Use ~/.dmd.d/ by default when not run as root Ludovic Courtès
2014-02-03 17:37 ` [PATCH 2/2] dmd: Make config file if necessary " Alex Sassmannshausen
2014-02-04 20:41 ` Ludovic Courtès
2014-02-05 18:27 ` Alex Sassmannshausen
2014-02-05 20:17 ` Ludovic Courtès
2014-02-04 20:34 ` dmd: make user-mode easier to use Ludovic Courtès
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=1391449065-19063-1-git-send-email-alex.sassmannshausen@gmail.com \
--to=alex.sassmannshausen@gmail.com \
--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 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.