Move guix.scm to scripts

The scripts directory already has several scripts that are not
needed to use libsamsung-ipc, but all of them are (or were) useful
to work on patches for libsamsung-ipc.

As this also applies to the guix.scm and that scheme is a scripting
language, it would be more clear to have it moved in the scripts
directory.

In addition it could also make it more simple for distributions
to not ship these files if they aren't interested in having them
and/or if they only want files compatibles with the license
currently used by libsamsung-ipc (GPLv2 or later).

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

1 files changed, 7 insertions, 6 deletions

diff --git a/guix.scm b/scripts/guix.scm
index fa23802..ec7b25c 100644
--- a/guix.scm
+++ b/scripts/guix.scm
@@ -29,11 +29,11 @@
 ;;; be interested in retrieving the source from git or releases tarballs.
 ;;;
 ;;; Once you have Guix installed, to build libsamsung-ipc with the
-;;; guix.scm file, you can use the 'guix build --file=guix.scm' command,
-;;; however as explained above, keep in mind that it will copy all the
-;;; files in the same directory than guix.scm, so you might want to
-;;; make sure that the sources are clean (with 'make distclean') if you
-;;; already built libsamsung-ipc in that directory.
+;;; guix.scm file, you can use the 'guix build --file=scripts/guix.scm'
+;;; command, however as explained above, keep in mind that it will copy
+;;; all the files in the same directory than guix.scm, so you might want
+;;; to make sure that the sources are clean (with 'make distclean') if
+;;; you already built libsamsung-ipc in that directory.
 ;;;
 ;;; While this file could also serve as a basis to make a libsamsung-ipc
 ;;; package in Guix, it is probably a good idea to wait until the API
@@ -72,7 +72,8 @@
 
 (define %local-source
   (local-file
-   (dirname (current-filename)) #:recursive? #t))
+    (dirname (dirname (current-filename)))
+   #:recursive? #t))
 
 (define-public libsamsung-ipc
   (package