I've had a problem like this before, when I was trying to build
the Shepherd from git.
On Wed, Apr 11 2018, Pierre Neidhardt wrote:
./configure: line 3350: config.log: Permission denied
I'm pretty sure this is what I had, and it was a problem of trying
to build in a directory that wa
Hi Pierre,
Pierre Neidhardt writes:
> Chris Marusich writes:
>
>> Can you share the package definition?
>
> Let's start from the most straight-forward:
>
> (define-public emacs-dev
> (package
>(inherit emacs)
>(name "emacs-dev")
>(version "26.0.91")
>(source
> (local-file
Hi Pierre,
> Chris Marusich writes:
>
>> Can you share the package definition?
>
> Let's start from the most straight-forward:
>
> (define-public emacs-dev
> (package
>(inherit emacs)
>(name "emacs-dev")
>(version "26.0.91")
>(source
> (local-file "/home/ambrevar/projects/
Ricardo Wurmus writes:
> Here’s mine:
>
> --8<---cut here---start->8---
> (define-public my/emacs
> (package (inherit emacs)
> (name "my-emacs")
> (version "26.0.91")
> [...]
> --8<---cut here---end--->8---
Note t
Chris Marusich writes:
> Can you share the package definition?
Let's start from the most straight-forward:
(define-public emacs-dev
(package
(inherit emacs)
(name "emacs-dev")
(version "26.0.91")
(source
(local-file "/home/ambrevar/projects/emacs-build" #:recursive? #t
Chris Marusich writes:
> Pierre Neidhardt writes:
>
>> Is there a good reason not to allow local paths in git URLs?
>
> You might find the "local-file" procedure to be helpful here. You can
> pass a local-file as the source of a package, which should allow you to
> define packages that use a l
Pierre Neidhardt writes:
> Mathieu Lirzin writes:
>
>> With the ‘#:recursive?’ keyword option set to #t, ‘local-file’ should
>> work for directories.
>
> Indeed, thanks for pointing out.
>
> I tried and it failed with
>
> starting phase `configure'
> source directory: "/tmp/guix-buil
Pierre Neidhardt writes:
> Is there a good reason not to allow local paths in git URLs?
You might find the "local-file" procedure to be helpful here. You can
pass a local-file as the source of a package, which should allow you to
define packages that use a local file path as the source. See (g
For now I'll stick to Emacs 26 RC1. I've adapted the package
declaration from "emacs" with the following changes:
- Disable the scheme patch.
- Disable tests.
Find the declaration attached.
--
Pierre Neidhardt
When you get your PH.D. will you get able to work at BURGER KING?
emacs.scm
Descr
Oleg Pykhalov writes:
> Pierre Neidhardt writes:
>
>> I tried reusing your package snippet from
>> http://lists.gnu.org/archive/html/help-guix/2017-09/msg00074.html by
>> setting
>>
>>(url "git://localhost/~ambrevar/projects/emacs")
>
> I'm sorry for probably an obvious question
Oleg Pykhalov writes:
>>> In case of ‘emacs’ package recipe, ‘--with-source’ doesn't work for a
>>> snapshot of the ‘master’ branch.
>>
>> Why? Because you’d need to run ‘autoreconf’ and the like?
>
> To run everything in ‘(arguments …)’ except ‘#:parallel-build? #t’.
>
> From http://lists.gnu.
Mathieu Lirzin writes:
> With the ‘#:recursive?’ keyword option set to #t, ‘local-file’ should
> work for directories.
Indeed, thanks for pointing out.
I tried and it failed with
starting phase `configure'
source directory: "/tmp/guix-build-emacs-dev-26.0.91.drv-0/source"
(re
Jorge writes:
> In my experience so
> far, these pretest versions are reliable enough for daily usage.
>
> Providing Emacs pretest versions would enable a larger audience to test them,
> thus helping the GNU project.
Very good points, I think.
--
Pierre Neidhardt
signature.asc
Description
March 27, 2018 6:51 AM, l...@gnu.org wrote:
> Pierre Neidhardt skribis:
>
>> Considering the importance of Emacs in this community, I think it would
>> make sense to provide a cutting-edge version.
>
> Do you mean a snapshot of the ‘master’ branch?
>
> We don’t do that usually, and I would inst
Pierre Neidhardt writes:
> I tried reusing your package snippet from
> http://lists.gnu.org/archive/html/help-guix/2017-09/msg00074.html by
> setting
>
>(url "git://localhost/~ambrevar/projects/emacs")
I'm sorry for probably an obvious question. Does ‘git clone
git://localhost/~
Pierre Neidhardt writes:
> Mathieu Lirzin writes:
>
>> I think you have to use the ‘local-file’ procedure in place of ‘origin’
>> in the ‘source’ field.
>
> Unless I'm mistaken, local-file does not work on folders. In the case
> of a Git repo, that would mean extracting the archive and overwrit
Mathieu Lirzin writes:
> I think you have to use the ‘local-file’ procedure in place of ‘origin’
> in the ‘source’ field.
Unless I'm mistaken, local-file does not work on folders. In the case
of a Git repo, that would mean extracting the archive and overwriting
the destination on each build.
Pierre Neidhardt writes:
> Oleg, I tried reusing your package snippet from
> http://lists.gnu.org/archive/html/help-guix/2017-09/msg00074.html
> by setting
>
>(url "git://localhost/~ambrevar/projects/emacs")
>
> but it fails for me:
[...]
> I'm not very familiar with the "git" pro
Oleg, I tried reusing your package snippet from
http://lists.gnu.org/archive/html/help-guix/2017-09/msg00074.html
by setting
(url "git://localhost/~ambrevar/projects/emacs")
but it fails for me:
> guix build -K emacs
@ build-started
/gnu/store/f3gbd1y74vw1my0fmzl
l...@gnu.org (Ludovic Courtès) writes:
> Oleg Pykhalov skribis:
[…]
>> In case of ‘emacs’ package recipe, ‘--with-source’ doesn't work for a
>> snapshot of the ‘master’ branch.
>
> Why? Because you’d need to run ‘autoreconf’ and the like?
To run everything in ‘(arguments …)’ except ‘#:paralle
Oleg Pykhalov skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Pierre Neidhardt skribis:
>>
>>> Considering the importance of Emacs in this community, I think it would
>>> make sense to provide a cutting-edge version.
>>
>> Do you mean a snapshot of the ‘master’ branch?
>>
>> We don’t do t
Oleg Pykhalov writes:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Pierre Neidhardt skribis:
>>
>>> Considering the importance of Emacs in this community, I think it would
>>> make sense to provide a cutting-edge version.
>>
>> Do you mean a snapshot of the ‘master’ branch?
>>
>> We don’t do th
l...@gnu.org (Ludovic Courtès) writes:
> Pierre Neidhardt skribis:
>
>> Considering the importance of Emacs in this community, I think it would
>> make sense to provide a cutting-edge version.
>
> Do you mean a snapshot of the ‘master’ branch?
>
> We don’t do that usually, and I would instead sug
Ludovic Courtès writes:
> Hello,
>
> Pierre Neidhardt skribis:
>
>> Considering the importance of Emacs in this community, I think it would
>> make sense to provide a cutting-edge version.
>
> Do you mean a snapshot of the ‘master’ branch?
>
> We don’t do that usually, and I would instead sugges
Hello,
Pierre Neidhardt skribis:
> Considering the importance of Emacs in this community, I think it would
> make sense to provide a cutting-edge version.
Do you mean a snapshot of the ‘master’ branch?
We don’t do that usually, and I would instead suggest using
‘--with-source’ for people who w
Considering the importance of Emacs in this community, I think it would
make sense to provide a cutting-edge version.
Is anyone willing to accept this?
--
Pierre Neidhardt
signature.asc
Description: PGP signature
Oleg Pykhalov writes:
> Hello Jorge,
>
> "Jorge" writes:
>
>> I would prefer to get Emacs 26 from Guix, which would be more
>> automatic and would come configured to work with Guix-installed Emacs
>> packages.
>
> Guix package collection provides only stable package releases for the
> most part.
March 3, 2018 7:24 AM, "Oleg Pykhalov" wrote:
> Guix package collection provides only stable package releases for the
> most part.
That's a pity.
> You could write a package recipe with a new version based on original
> recipe, see [1].
>
> Also you could try ‘--with-source’ [2], but in Emacs ca
Hello Jorge,
"Jorge" writes:
> I would prefer to get Emacs 26 from Guix, which would be more
> automatic and would come configured to work with Guix-installed Emacs
> packages.
Guix package collection provides only stable package releases for the
most part.
> So is Emacs 26 available from Guix
Hi. I use Spacemacs v.0.300.0 (develop) atop Emacs 26.0.91. I compile
Emacs 26 locally and stow it with GNU Stow. I would prefer to get Emacs
26 from Guix, which would be more automatic and would come configured to
work with Guix-installed Emacs packages. So is Emacs 26 available from
Guix? Un
30 matches
Mail list logo