On 2010/01/25, at 15:46 , Faré wrote:
OK, the ASDF my repo now supports source-registry.conf.d as well as
source-registry.conf. I'll commit it upstream by next week unless I
get negative feedback, and hopefully after including some tests.
Note that at least clisp seems confused when matching
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19/01/10 21:52, James Y Knight wrote:
Only root would be able to use clc-clbuild, right?
Correct. Except for clc-clbuild slime which should start an emacs with
slime running.
This mostly works (I had to do some patched to clbuild itself).
I
OK, the ASDF my repo now supports source-registry.conf.d as well as
source-registry.conf. I'll commit it upstream by next week unless I
get negative feedback, and hopefully after including some tests.
Note that at least clisp seems confused when matching *.* or
(make-pathname :type :wild :name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Faré,
I was actually thinking about this feature of yours in the traffic jam:
instead of /etc/common-lisp/source-registry.conf I would like to see
/etc/common-lisp/source-registry.conf.d
where instead of having one file that you might have
2010/1/20 Peter Van Eynde pvane...@mailworks.org:
instead of /etc/common-lisp/source-registry.conf I would like to see
/etc/common-lisp/source-registry.conf.d
where instead of having one file that you might have to edit in
post-installation scripts we would have a directory where packages can
On Jan 12, 2010, at 11:10 AM, Peter Van Eynde wrote:
Hello James,
Just FYI I've started working on CLC v7 where this will be a system-
wide
setting overrideable with a user-specific configuration file.
Thanks for the info.
I'd still like to hear if you have any more specifics about the
On Jan 14, 2010, at 12:41 AM, Peter Van Eynde wrote:
My current plan was to:
- - make the inclusion of the CLC directory configurable
- - add clbuild support to the package:
* clbuild would get downloaded and updated on the client machine
* we would have a new command clc-clbuild which
Dear Peter,
BTW, I committed my changes to ASDF, in my current development repo at
http://common-lisp.net/gitweb?p=projects/xcvb/asdf.git
If no one complains (and I don't suppose anyone will), this will get
distributed as ASDF 1.500 next week.
(I bumped the version to a round number forward, to
I guess my ideal debian lisp integration would be:
$ apt-get install sbcl cl-cffi
- I have actual FASL files on disk that sbcl can use, so that
(require :cffi) just has to load them: no compilation necessary.
But since that seems infeasible, second best would be:
Works like today, where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Faré,
On 12/01/10 17:46, Faré wrote:
Can you make the path to those files compatible with what I'm
preparing for ASDF?
I've taken a look at the bug and the idea seems to be to have a place to
define the locations of systems in on a system
Hi Peter,
Can you make the path to those files compatible with what I'm
preparing for ASDF?
I've taken a look at the bug and the idea seems to be to have a place to
define the locations of systems in on a system and user level. Right?
For path configuration, if I get my way with ASDF, you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello James,
Just FYI I've started working on CLC v7 where this will be a system-wide
setting overrideable with a user-specific configuration file.
Groetjes, Peter
- --
signature -at- pvaneynd.mailworks.org
2010/1/12 Peter Van Eynde pvane...@debian.org:
Just FYI I've started working on CLC v7 where this will be a system-wide
setting overrideable with a user-specific configuration file.
Can you make the path to those files compatible with what I'm
preparing for ASDF?
My current file paths are
This change was done so that using for example clbuild in Debian
becomes
possible again. Otherwise the packaged systems will interfere with the
clbuild or locally generated systems.
I still don't understand. The new behavior, even though now
documented, breaks all user expectations for how
Package: common-lisp-controller
Version: 6.19
When I upgraded CLC from 6.17 to 6.20, neither
(require 'cffi)
nor
(asdf:oos 'asdf:compile-op :cffi)
work anymore, even though the cl-cffi package is installed.
Looking at the changelog, it seems like this was an intentional change in 6.19,
Make clc
15 matches
Mail list logo
