> "--disable-shared" "LDFLAGS=-static"
Bash doesn't have '--disable-shared'. I used these commands:
# export LDFLAGS=-static
# ./configure --without-bash-malloc \
--disable-readline \
--disable-history \
--disable-help-builtin \
--disable-
Andreas Enge skribis:
> While trying to add a package to compression.scm, I just added the line
> #:use-module (gnu packages python)
[...]
> 2667: 9 [define-module* (gnu packages python) #:filename ...]
> 2642: 8 [resolve-imports ((# # #) (#) (#) (#) ...)]
> 2580: 7 [resolve-interface (gnu pa
While trying to add a package to compression.scm, I just added the line
#:use-module (gnu packages python)
This results in the following error:
Backtrace:
In ice-9/eval.scm:
392: 19 [eval # ()]
In ice-9/boot-9.scm:
2667: 18 [define-module* (gnu packages compression) #:filename ...]
2642: 17 [re
Cyril Roelandt skribis:
> * gnu/packages/subversion.scm: New file.
> * Makefile.am (MODULES): Add it.
Applied.
> + #:use-module (guix licenses)
Here I added #:select to avoid the name clash for ‘zlib’.
> + (uri (string-append
> +
> "http://mirrors.ircam.fr/pub/
Cyril Roelandt skribis:
> * gnu/packages/sqlite.scm: New file.
> * Makefile.am (MODULES): Add it.
Applied, thanks.
> +(uri (string-append
> +
> "http://downloads.sourceforge.net/project/sqlite.mirror/SQLite%20";
> + version "/sqlite-autoconf-307150
Cyril Roelandt skribis:
> * gnu/packages/libapr.scm: New file.
> * gnu/packages/patches/libapr-skip-getservbyname-test.patch: New file
> * Makefile.am: Add them
> * gnu/packages/libapr: new variable.
Applied both, thanks!
Ludo’.
Hello !
This patch series adds Subversion and its dependencies, which probably will be
useful for other packages as well.
Regards,
Cyril Roelandt.
---
Cyril Roelandt (4):
Add lipabr.
Add libaprutil.
Add SQLite.
Add Subversion.
Makefile.am|4
* gnu/packages/subversion.scm: New file.
* Makefile.am (MODULES): Add it.
---
Makefile.am |1 +
gnu/packages/subversion.scm | 59 +++
2 files changed, 60 insertions(+)
create mode 100644 gnu/packages/subversion.scm
diff --git a/Makefi
* gnu/packages/sqlite.scm: New file.
* Makefile.am (MODULES): Add it.
---
Makefile.am |1 +
gnu/packages/sqlite.scm | 49 +++
2 files changed, 50 insertions(+)
create mode 100644 gnu/packages/sqlite.scm
diff --git a/Makefile.am b/Make
* gnu/packages/libapr: new variable.
---
gnu/packages/libapr.scm | 33 +
1 file changed, 33 insertions(+)
diff --git a/gnu/packages/libapr.scm b/gnu/packages/libapr.scm
index 36f0e1e..b342e77 100644
--- a/gnu/packages/libapr.scm
+++ b/gnu/packages/libapr.scm
@@ -
* gnu/packages/libapr.scm: New file.
* gnu/packages/patches/libapr-skip-getservbyname-test.patch: New file
* Makefile.am: Add them
---
Makefile.am|2 +
gnu/packages/libapr.scm| 58
.../patches/libapr-ski
Nikita Karetnikov skribis:
>> 3. More generally, should the history of generations be linear, or
>> should it be a DAG like Git commits?
>
> If the latter is the case, then we can probably use a simple tree. Here
> is a related link: [1].
Right, if we went for a tree, each manifest could c
Am Freitag, 25. Januar 2013 schrieb Alex Sassmannshausen:
> I guess a generation would only be destroyed at a junction, not when
> moving back and forth in straight lines.
> A --> B --> C
> You could travel from C back to A and back to C without having to
> re-install packages...
Yes, that
> > Let me illustrate. Suppose these generations:
>
> > A --> B --> C
>
> > When doing a roll-back from C, one should obviously get back at B. At
> > that point, C would still be available. Keeping it around means that
> > users can easily switch back to C if B turned out to be less
14 matches
Mail list logo
