cclan-list — Discussions of all things CCLAN

[cclan-list] Consolidating Common Lisp Libraries

[Faré <fa...@gm...>]

I've started an initiative to consolidate CL libraries:
http://fare.livejournal.com/169346.html

Is it appropriate to reactivate the cCLan list toward discussion on
such consolidation?

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
Necessity is the plea for every infringement of human freedom.
It is the argument of tyrants; it is the creed of slaves. — William Pitt, 1783

Re: [cclan-list] XCVB patch for split-sequence

[Christophe R. <cs...@ca...>]

Faré <fa...@gm...> writes:

> Can it be applied upstream?

Gah, why did you send the same content to two lists, without even
cross-posting?  Please see my reply on asdf-devel.

Best,

Christophe

[cclan-list] XCVB patch for split-sequence

[Faré <fa...@gm...>]

Can it be applied upstream?

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
They laughed at Columbus, they laughed at Fulton, they laughed at the
Wright brothers.  But they also laughed at Bozo the Clown.
                -- Carl Sagan

Re: [cclan-list] How to depend on a system optionally?

[Tobias C. R. <tc...@fr...>]

Nikodemus Siivola <nik...@ra...> writes:

> Doesn't :WEAKLY-DEPENDS-ON do what you want?

Yes, that seems to be it. (Notice that it's not documented.)

Thanks!

  -T.

Re: [cclan-list] How to depend on a system optionally?

[james a. <jam...@se...>]

hello;

in order to manage a system for multiple runtimes, each of which  
entails it's own foreign libraries, i have found it useful to add a  
constraint called "contingent-on". this may-or-may-not be what you  
intend with "optionally-depend-on". i have found it useful to express  
the constraints:

  "if a feature|system is present, then this system|component is  
required, and depends on it."


On 2009-05-18, at 14:28 , Tobias C. Rittweiler wrote:

>
> I've read several times that it's a head ache to configure optional
> dependencies with ASDF.
>
> How true is that? Could we perhaps provide another clause
> :OPTIONALLY-DEPEND-ON in DEFSYSTEM which would load a system only if
> available?
>
> Reason is that I'm going to revive
>
>   http://common-lisp.net/project/hyperdoc/
>
> which is a good example of a natural optional dependency. And I'd like
> to make its inclusion as easy as possible so it'll see widespread
> adoption.
>
> Thanks!,
>
>   -T.
>
>
> ---------------------------------------------------------------------- 
> --------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> cclan-list mailing list
> ccl...@li...
> https://lists.sourceforge.net/lists/listinfo/cclan-list

Re: [cclan-list] How to depend on a system optionally?

[Nikodemus S. <nik...@ra...>]

2009/5/18 Robert Goldman <rpg...@si...>:
> Tobias C. Rittweiler wrote:
>> I've read several times that it's a head ache to configure optional
>> dependencies with ASDF.
>>
>> How true is that? Could we perhaps provide another clause
>> :OPTIONALLY-DEPEND-ON in DEFSYSTEM which would load a system only if
>> available?

Doesn't :WEAKLY-DEPENDS-ON do what you want?

Cheers,

 -- Nikodemus

Re: [cclan-list] How to depend on a system optionally?

[Robert G. <rpg...@si...>]

Tobias C. Rittweiler wrote:
> I've read several times that it's a head ache to configure optional
> dependencies with ASDF. 
> 
> How true is that? Could we perhaps provide another clause
> :OPTIONALLY-DEPEND-ON in DEFSYSTEM which would load a system only if
> available?
> 
> Reason is that I'm going to revive
> 
>   http://common-lisp.net/project/hyperdoc/
> 
> which is a good example of a natural optional dependency. And I'd like
> to make its inclusion as easy as possible so it'll see widespread
> adoption.
> 

I thought that Gary already had a scheme for doing this.  I'm afraid I
know no more (I wish some of Gary's add-ons, like the invaluable
asdf-binary-locations, would just come with ASDF, though not turned on
by default...).

BTW, Gary has been trying to wean us off cclan-list@ sourceforge and
onto asd...@co....

best,
r

[cclan-list] How to depend on a system optionally?

[Tobias C. R. <tc...@fr...>]

I've read several times that it's a head ache to configure optional
dependencies with ASDF. 

How true is that? Could we perhaps provide another clause
:OPTIONALLY-DEPEND-ON in DEFSYSTEM which would load a system only if
available?

Reason is that I'm going to revive

  http://common-lisp.net/project/hyperdoc/

which is a good example of a natural optional dependency. And I'd like
to make its inclusion as easy as possible so it'll see widespread
adoption.

Thanks!,

  -T.

[cclan-list] sourceforge website + cliki

[Gary K. <gw...@me...>]

I've updated the sourceforge cclan page (http:// 
cclan.sourceforge.net/) to point towards asdf's new home. I've also  
updated the cliki.

(next step, mailing lists...)
--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM * gwking on twitter

Re: [cclan-list] git repo on cl.net trashed?!

[Gary K. <gw...@me...>]

(cc'd to list)

Thanks Daniel,

I bow to your git fu <smile>

The problem was the permissions of the directories in objects. I  
thought I had fixed these already but ... In any case, making all of  
these drwsrwsr-w seems to do the trick.

> gking@cl-net:/project/asdf/public_html/asdf.git$ git fsck
> dangling commit 22b407fd3be1f1515d2b7a0143c07376c82f3f30

I've pulled Nikodemus's push and  I've pushed some minor website and  
formatting tweaks of my own so things seem one step closer to working.

thanks,

On May 7, 2009, at 10:15 PM, dhe...@te... wrote:

> FWIW, the following objects are stored in the objects directory (if  
> bare,
> .git/objects else).  So 00fe92.. should be found in objects/00/fe93...
>
>>> error: 00fe921ca3660cd116825f76a56b4912f878857c: object corrupt or
>>> missing
> ...
>
> You'll notice these broken links point to objects in the above list.
>>> broken link from    tree f3ddd609fef1183f3778d22a599e1029de74b4ce
>>>              to    blob 3d50e41634b4ba657bd0aedf9b5c51516d6d3da0
>>> broken link from    tree f3ddd609fef1183f3778d22a599e1029de74b4ce
>>>              to    tree 00fe921ca3660cd116825f76a56b4912f878857c
>>> broken link from  commit ddcf33a539faa728751f70591b2b781f057340e1
>>>              to  commit c457de74d45d34be385c2721cd4eaa449a756f93
>>> missing tree 00fe921ca3660cd116825f76a56b4912f878857c
>>> missing commit c457de74d45d34be385c2721cd4eaa449a756f93
>>> dangling commit 22b407fd3be1f1515d2b7a0143c07376c82f3f30
>>> missing blob 3d50e41634b4ba657bd0aedf9b5c51516d6d3da0
>>
>> I'm assuming that I caused bad things to happen somehow when  
>> repairing
>> permissions. If no one complains (by sometime tomorrow), I'm going to
>> recreate the repo from what I have locally.
>
> I'd be surprised if its a permissions thing; but who knows.  Your  
> local
> git repo should have the missing objects (or git-fsck should give  
> the same
> errors locally) so you should be able to simply copy them to cl.net if
> they are in fact missing.
>
> - Daniel
>
>

--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM * gwking on twitter

[cclan-list] git repo on cl.net trashed?!

[Gary K. <gw...@me...>]

git fsck reports

> error: 00fe921ca3660cd116825f76a56b4912f878857c: object corrupt or  
> missing
> error: 096cce2612b7f59f1e8a8deaf6c2b851107bc4f8: object corrupt or  
> missing
> error: 348c263634970492274e8b61b2745085c23f557d: object corrupt or  
> missing
> error: 34dba06e0230a509730dc18a758cdbaadc80900b: object corrupt or  
> missing
> error: 3d50e41634b4ba657bd0aedf9b5c51516d6d3da0: object corrupt or  
> missing
> error: 5439294a26289e7e7c08e2b7085202f6488a31bc: object corrupt or  
> missing
> error: 9586a60d3824bd2fa958e548363a6cccd798588f: object corrupt or  
> missing
> error: 9cc3ccd8d61651c471c2c7123f3f47e9042bd84b: object corrupt or  
> missing
> error: c457de74d45d34be385c2721cd4eaa449a756f93: object corrupt or  
> missing
> error: cd42d4c39c2c95dc31ccad4124eddfc8795c5622: object corrupt or  
> missing
> error: d1d8f4db86dfb5ef2b0847f96999bf7e0235afe0: object corrupt or  
> missing
> error: e29f0a6aceb11db6ec5a8b6fa284bdc7f6da8c08: object corrupt or  
> missing
> broken link from    tree f3ddd609fef1183f3778d22a599e1029de74b4ce
>               to    blob 3d50e41634b4ba657bd0aedf9b5c51516d6d3da0
> broken link from    tree f3ddd609fef1183f3778d22a599e1029de74b4ce
>               to    tree 00fe921ca3660cd116825f76a56b4912f878857c
> broken link from  commit ddcf33a539faa728751f70591b2b781f057340e1
>               to  commit c457de74d45d34be385c2721cd4eaa449a756f93
> missing tree 00fe921ca3660cd116825f76a56b4912f878857c
> missing commit c457de74d45d34be385c2721cd4eaa449a756f93
> dangling commit 22b407fd3be1f1515d2b7a0143c07376c82f3f30
> missing blob 3d50e41634b4ba657bd0aedf9b5c51516d6d3da0

I'm assuming that I caused bad things to happen somehow when repairing  
permissions. If no one complains (by sometime tomorrow), I'm going to  
recreate the repo from what I have locally.


--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM * gwking on twitter

Re: [cclan-list] git repository for ASDF

[Nikodemus S. <nik...@ra...>]

2009/5/5 Gary King <gw...@me...>:
> Got 'em.
>
> (I think I was (am!) confused about sticky bit versus setuid bit. We want
> the latter, not the former, right?

Oops, actually, my terms were reversed. We want the SGID, aka set
group id bit on directories -- not the sticky bit. It's right in the
asdf-new.git tree, it's the bit that shows up as an 's' in the group
permissions when combined with exec permissions. Those bits are as
they are supposed to be in the asdf-new.git tree.

(We want it in order to have files created in those directories have
the same group as the directory, as opposed to whatever happens to be
the primary group of the user at that moment.)

Cheers,

 -- Nikodemus

Re: [cclan-list] git repository for ASDF

[Gary K. <gw...@me...>]

Got 'em.

(I think I was (am!) confused about sticky bit versus setuid bit. We  
want the latter, not the former, right?


On May 5, 2009, at 12:09 PM, Nikodemus Siivola wrote:

> 2009/5/5 Gary King <gw...@me...>:
>
>>> replace the main repository, nor can I fix its permissions as the
>>> project directory itself is missing group write permissions, and the
>>> public_html directory is missing group write and sticky bit.
>
>> Fixed (I think)
>
> No group write in the project directory:
>
>  drwxr-sr-x 4 mbaringer asdf 4096 2009-05-05 08:48 /project/asdf/
>
> should be drwxrwsr-x.
>
> No group sticky bit in public_html (instead deletion is restricted  
> to owner):
>
>  drwxrwxr-t 4 gking asdf 4096 2009-05-05 11:03 /project/asdf/ 
> public_html/
>
> should be drwxrwsr-x as well.
>
>>> For the directory and all subdirectories: dwrxrwsr-x (note the group
>>> sticky bit)
>>
>> ok
>
> Enough of the asdf.git permissions are still out of whack to render
> the repo inoperable (missing write and directory access permissions,
> plus unhygienic write permissions in places where there should be
> none.)
>
> A fixed repo, which should have the group permissions right is now at
>
>   /project/asdf/public_html/asdf-new.git
>
> -- it has the same objects as the earlier one, plus one new commit on
> top. I would have replaced the broken one, but due to the t bit in
> public_html/ I still could not. If you can verify that this one works
> for you (test pushing as well...), then just renaming it to asdf.git
> should have us up and running.
>
> For future reference, I belatedly realized that the easiest way to fix
> things was to make a new empty repo that had the right group and was
> initialized with --shared=group, and then push everything from a
> working clone there:
>
>  cd ~/
>  newgrp asdf
>  mkdir asdf.git
>  chmod g+ws asdf.git
>  cd asdf.git
>  git init --bare --shared=group
>
> and then from my home machine:
>
>  cd src/asdf-git # a working clone made from the old asdf.git
>  git push ssh://nsi...@co.../home/nsiivola/asdf.git master
>
> and finally on common-lisp.net
>
>  cd /project/asdf/public_html
>  mv ~/asdf.git asdf-new.git
>
> Cheers,
>
> -- Nikodemus
>
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances!  
> Your
> production scanning environment may not be a perfect world - but  
> thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW  
> KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> cclan-list mailing list
> ccl...@li...
> https://lists.sourceforge.net/lists/listinfo/cclan-list

--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM * gwking on twitter

Re: [cclan-list] git repository for ASDF

[Nikodemus S. <nik...@ra...>]

2009/5/5 Gary King <gw...@me...>:

>> replace the main repository, nor can I fix its permissions as the
>> project directory itself is missing group write permissions, and the
>> public_html directory is missing group write and sticky bit.

> Fixed (I think)

No group write in the project directory:

  drwxr-sr-x 4 mbaringer asdf 4096 2009-05-05 08:48 /project/asdf/

should be drwxrwsr-x.

No group sticky bit in public_html (instead deletion is restricted to owner):

  drwxrwxr-t 4 gking asdf 4096 2009-05-05 11:03 /project/asdf/public_html/

should be drwxrwsr-x as well.

>> For the directory and all subdirectories: dwrxrwsr-x (note the group
>> sticky bit)
>
> ok

Enough of the asdf.git permissions are still out of whack to render
the repo inoperable (missing write and directory access permissions,
plus unhygienic write permissions in places where there should be
none.)

A fixed repo, which should have the group permissions right is now at

   /project/asdf/public_html/asdf-new.git

-- it has the same objects as the earlier one, plus one new commit on
top. I would have replaced the broken one, but due to the t bit in
public_html/ I still could not. If you can verify that this one works
for you (test pushing as well...), then just renaming it to asdf.git
should have us up and running.

For future reference, I belatedly realized that the easiest way to fix
things was to make a new empty repo that had the right group and was
initialized with --shared=group, and then push everything from a
working clone there:

  cd ~/
  newgrp asdf
  mkdir asdf.git
  chmod g+ws asdf.git
  cd asdf.git
  git init --bare --shared=group

and then from my home machine:

  cd src/asdf-git # a working clone made from the old asdf.git
  git push ssh://nsi...@co.../home/nsiivola/asdf.git master

and finally on common-lisp.net

  cd /project/asdf/public_html
  mv ~/asdf.git asdf-new.git

Cheers,

 -- Nikodemus

Re: [cclan-list] asdf on cl.net -- beta

[Gary K. <gw...@me...>]

I would like to move the cClan list to cl.net (including the archives,  
etc.).

I'm of course open to other opinions and ideas.

On May 5, 2009, at 9:22 AM, Richard M Kreuter wrote:

> Gary King writes:
>> Hi all,
>>
>> Please look at http://common-lisp.net/project/asdf and tell me what
>> you think.
>
> Point of order: will the cclan-list cease to be the place to discuss
> ASDF activity?
>
> --
> RmK
>
>
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances!  
> Your
> production scanning environment may not be a perfect world - but  
> thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW  
> KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> cclan-list mailing list
> ccl...@li...
> https://lists.sourceforge.net/lists/listinfo/cclan-list

--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM * gwking on twitter

Re: [cclan-list] asdf on cl.net -- beta

[Richard M K. <kr...@pr...>]

Gary King writes:
> Hi all,
> 
> Please look at http://common-lisp.net/project/asdf and tell me what  
> you think.

Point of order: will the cclan-list cease to be the place to discuss
ASDF activity?

--
RmK

Re: [cclan-list] git repository for ASDF

[Robert G. <rpg...@si...>]

Gary King wrote:
> Hi Robert,
> 
>> As I understand things, we should, if we are working on a particular
>> improvement, move ourselves onto a branch, make our changes, and then
>> offer up the changes for some flavor of review, right?
> 
> I'm pretty new to git myself but am trying to use something like this  
> workflow
> 
> http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html
> 
>> Can someone explain to me how the final step is done?  I have only  
>> done
>> this using org, where my changes were small enough that they could be
>> eyeballed in patch files.
> 
> A Nikodemus suggested, I think sending a patch to the mailing list  
> would be the best thing for now.

My concern arose about shipping around patches involving the addition of
multiple files (this arises when creating new tests for asdf).
[...snip...]
> 
>> I am very excited about the institution of the git repo, though, since
>> the changes I am making, although they are modest (and most of the  
>> work
>> is another's), they do involve non-local changes, and really seem to
>> exceed what one can comfortably do with CVS.
> 
> Yeah! Why don't you send the patch when you're ready and we can try to  
> make asdf:clean-op a test case.

Will do.  I shelved this for a long while because I wasn't sure how to
deal with creating the new test cases with only CVS to rely on.  Might
take me a little while to recover the context.

Best,
R

Re: [cclan-list] git repository for ASDF

[Gary K. <gw...@me...>]

> Digging deeper, I'm guessing you didn't initialize the repo using
> --shared=group at all, so the permissions didn't get set right in the
> first place, and I think setting that flag (which I managed to do) is
> not enough to fix them.

Whoopts. That's right. I didn't

> I made a copy in ~nsiivola on common-lisp.net, and tried to fix the
> permissions there, and while I think I got them right, I cannot
> replace the main repository, nor can I fix its permissions as the
> project directory itself is missing group write permissions, and the
> public_html directory is missing group write and sticky bit.
>

Fixed (I think)

> As for asdf.git, I believe the correct permissions are as follows:
>
> For the directory and all subdirectories: dwrxrwsr-x (note the group
> sticky bit)

ok

>
> For files under objects/??/ and objects/pack/: -r--r--r--

ok

>
> For files under hooks/, -rwxrwxr-x

ok

>
> For all other files, including those under objects/info/: -rw-rw-r--

ok
>
>
> ...and the group should be asdf everywhere, of course (it's currently
> users on a few subdirectories.)
>
ok

> (I managed to fix the complete one push by accident, since I was
> allowed to create *new* directories under objects/, and was able to
> fix some of the permissions. Other than the messed up permissions and
> ownerships, it looks healthy to me.)
>


Can you please check again.

What about these three new files

> -rw-rwSr--  1 nsiivola asdf  117 2009-05-05 03:44 config
> -rw-rwSr--  1 nsiivola asdf   58 2009-05-05 03:44 description
> -rw-rwSr--  1 nsiivola asdf   23 2009-05-05 03:44 HEAD

Let me know if I should just try creating it again...

--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM * gwking on twitter

Re: [cclan-list] git repository for ASDF

[Gary K. <gw...@me...>]

Hi Robert,

> As I understand things, we should, if we are working on a particular
> improvement, move ourselves onto a branch, make our changes, and then
> offer up the changes for some flavor of review, right?

I'm pretty new to git myself but am trying to use something like this  
workflow

http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html

> Can someone explain to me how the final step is done?  I have only  
> done
> this using org, where my changes were small enough that they could be
> eyeballed in patch files.

A Nikodemus suggested, I think sending a patch to the mailing list  
would be the best thing for now.

(Once the repo is straightened out), I am going to add an unstable  
branch into which patches will go first.

> But I have been working to get Marco's CLEAN-OP incorporated into  
> ASDF,
> and this involves adding files (notably in order to make tests).  This
> puts me, I think, beyond the realm of easily reviewed patches.  In  
> this
> case does one provide a branch in the common-lisp.net repo?  Should  
> one
> create one's own public repository?

I agree with Nikodemus (again! <smile>)

> I have read some of the git tutorials but evidently I have not read  
> the
> right ones, since the answers to these questions still elude me.

I think that git is so flexible that knowing exactly what to do when  
is elusive. We'll have to create a path by walking.

> I am very excited about the institution of the git repo, though, since
> the changes I am making, although they are modest (and most of the  
> work
> is another's), they do involve non-local changes, and really seem to
> exceed what one can comfortably do with CVS.

Yeah! Why don't you send the patch when you're ready and we can try to  
make asdf:clean-op a test case.

--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM * gwking on twitter

Re: [cclan-list] git repository for ASDF

[Nikodemus S. <nik...@ra...>]

2009/5/5 Nikodemus Siivola <nik...@ra...>:
> The repo still doesn't seem set up quite right. When I try to push, I get:
>
> Counting objects: 5, done.
> Compressing objects: 100% (3/3), done.
> Writing objects: 100% (3/3), 382 bytes, done.
> Total 3 (delta 2), reused 0 (delta 0)
> error: Unable to append to logs/HEAD: Permission denied
> To ssh://nsi...@co.../project/asdf/public_html/asdf.git
>   c457de7..ddcf33a  master -> master
>
> I believe this is because core.sharedRepository is not set correctly.
> See "git help config":
>
>  http://www.kernel.org/pub/software/scm/git/docs/git-config.html

Digging deeper, I'm guessing you didn't initialize the repo using
--shared=group at all, so the permissions didn't get set right in the
first place, and I think setting that flag (which I managed to do) is
not enough to fix them.

I made a copy in ~nsiivola on common-lisp.net, and tried to fix the
permissions there, and while I think I got them right, I cannot
replace the main repository, nor can I fix its permissions as the
project directory itself is missing group write permissions, and the
public_html directory is missing group write and sticky bit.

As for asdf.git, I believe the correct permissions are as follows:

 For the directory and all subdirectories: dwrxrwsr-x (note the group
sticky bit)
 For files under objects/??/ and objects/pack/: -r--r--r--
 For files under hooks/, -rwxrwxr-x
 For all other files, including those under objects/info/: -rw-rw-r--

...and the group should be asdf everywhere, of course (it's currently
users on a few subdirectories.)

(I managed to fix the complete one push by accident, since I was
allowed to create *new* directories under objects/, and was able to
fix some of the permissions. Other than the messed up permissions and
ownerships, it looks healthy to me.)

Cheers,

 -- Nikodemus

Re: [cclan-list] git repository for ASDF

[Nikodemus S. <nik...@ra...>]

The repo still doesn't seem set up quite right. When I try to push, I get:

Counting objects: 5, done.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 382 bytes, done.
Total 3 (delta 2), reused 0 (delta 0)
error: Unable to append to logs/HEAD: Permission denied
To ssh://nsi...@co.../project/asdf/public_html/asdf.git
   c457de7..ddcf33a  master -> master

I believe this is because core.sharedRepository is not set correctly.
See "git help config":

  http://www.kernel.org/pub/software/scm/git/docs/git-config.html

Cheers,

 -- Nikodemus

Re: [cclan-list] git repository for ASDF

[Nikodemus S. <nik...@ra...>]

2009/5/4 Robert Goldman <rpg...@si...>:
> As I understand things, we should, if we are working on a particular
> improvement, move ourselves onto a branch, make our changes, and then
> offer up the changes for some flavor of review, right?
>
> Can someone explain to me how the final step is done?  I have only done
> this using org, where my changes were small enough that they could be
> eyeballed in patch files.

Since we have not discussed it, I assume sending patches to the
mailing list remains the preferred format.

> But I have been working to get Marco's CLEAN-OP incorporated into ASDF,
> and this involves adding files (notably in order to make tests).  This
> puts me, I think, beyond the realm of easily reviewed patches.

Not really: with git those patches are best produced using "git
format-patch -<small integer", which deals with new files just fine.

> In this case does one provide a branch in the common-lisp.net repo?  Should one
> create one's own public repository?

To the first, I would say no. I would suggest that we don't add
feature branches to the main repository. Adding an "unstable" branch
might be worth considering, though -- and put new features and API
changes there initially.

To the second, I would say that it's not really necessary. Not unless
you feel that your work is being ignored, or unless you know that
there are people who want to pull from yourself, or because you figure
you want a backup for your local tree...

Cheers,

 -- Nikodemus

Re: [cclan-list] git repository for ASDF

[Robert G. <rpg...@si...>]

As I understand things, we should, if we are working on a particular
improvement, move ourselves onto a branch, make our changes, and then
offer up the changes for some flavor of review, right?

Can someone explain to me how the final step is done?  I have only done
this using org, where my changes were small enough that they could be
eyeballed in patch files.

But I have been working to get Marco's CLEAN-OP incorporated into ASDF,
and this involves adding files (notably in order to make tests).  This
puts me, I think, beyond the realm of easily reviewed patches.  In this
case does one provide a branch in the common-lisp.net repo?  Should one
create one's own public repository?

I have read some of the git tutorials but evidently I have not read the
right ones, since the answers to these questions still elude me.

I am very excited about the institution of the git repo, though, since
the changes I am making, although they are modest (and most of the work
is another's), they do involve non-local changes, and really seem to
exceed what one can comfortably do with CVS.

Best,
R

[cclan-list] asdf on cl.net -- beta

[Gary K. <gw...@me...>]

Hi all,

Please look at http://common-lisp.net/project/asdf and tell me what  
you think.

One question I have is what to do with the copyright. I changed it to  
read

> Copyright (c) 2009 Gary King and contributors (gw...@me...)
> Copyright (c) 2001-2008 Daniel Barlow and contributors

but don't feel completely comfortable about that. Can we just make it  
some variant of creative commons or have it be jointly copyright in  
the names of all of the authors?

Once folks have had a chance to look at this, I'll modify the  
SourceForge pages to re-direct here and make an announcement.


--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM * gwking on twitter

Re: [cclan-list] ASDF:OPERATE should bind *PACKAGE* and *READTABLE*

[Gary K. <gw...@me...>]

If we could wait on this until the git switch is complete (RSN,  
really), I think I'd dance naked in the streets. No, not really. But I  
do think it would be a good thing.

:-)

On Apr 29, 2009, at 5:42 PM, Nikodemus Siivola wrote:

> 2009/4/30 Richard M Kreuter <kr...@pr...>:
>> Nikodemus Siivola writes:
>>
>>> IMO ASDF:OPERATE is sufficiently akin to LOAD and COMPILE-FILE, that
>>> it too should bind package and readtable. Attached patch does this.
>>> Unless cries of outrage are heard, I'll merge this soonish.
>>
>> I agree.  (Out of curiosity, did you find a system in the wild for  
>> which
>> not rebinding those two variables produced undesirable results?)
>
> Any system using a CFFI-GROVEL component left the package in whatever
> the CFFI-GROVEL component used -- eg. iolib. The CFFI misbehaviour has
> now been fixed in upstream, but I think ASDF should be robust in the
> face of such issues.
>
> Cheers,
>
> -- Nikodemus
>
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code  
> vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> cclan-list mailing list
> ccl...@li...
> https://lists.sourceforge.net/lists/listinfo/cclan-list

--
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM * gwking on twitter