Re: [Chicken-users] Re: [Chicken-hackers] egg-post-commit
On 3/8/07, Alejandro Forero Cuervo <[EMAIL PROTECTED]> wrote: > Out of curiosity --- if an egg doesn't have a 'tags' (and 'trunk') > directory, it is possible to modify it so that it does? Not only possible, it is also worthwhile. :-) You can do this by doing: [snip] Excellent -- thank you, Alejo, that looks very easy. Graham ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Re: [Chicken-hackers] egg-post-commit
> Out of curiosity --- if an egg doesn't have a 'tags' (and 'trunk') > directory, it is possible to modify it so that it does? Not only possible, it is also worthwhile. :-) You can do this by doing: cd $EGG mkdir trunk tags svn add trunk tags for file in *; do svn mv $file trunk; done; svn commit -m "Moving all the code to the trunk." Commit and then follow the instructions in “Making a release” at: http://chicken.wiki.br/eggs%20tutorial#Making%20a%20new%20release That should do it. :-) Alejo. http://azul.freaks-unidos.net/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Re: [Chicken-hackers] egg-post-commit
2007/3/8, Alejandro Forero Cuervo <[EMAIL PROTECTED]>: > >What if the directory contains multiple eggs ? > >I ask this because I think I'll end up with lot of eggs for the > >gl-suite project. > >Is it better to have, gl-display-*, gl-font, gl-math, gl-repl, > >gl-samples, gl-etcaetera, > >or simply gl-suite ? > >(If the former, Felix, prepare to have more request from me:) > > On directory, one egg, please. Yeah, I totally agree: no directory in Chicken-eggs should have more than one egg. :) Fine thu ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Re: [Chicken-hackers] egg-post-commit
> >What if the directory contains multiple eggs ? > >I ask this because I think I'll end up with lot of eggs for the > >gl-suite project. > >Is it better to have, gl-display-*, gl-font, gl-math, gl-repl, > >gl-samples, gl-etcaetera, > >or simply gl-suite ? > >(If the former, Felix, prepare to have more request from me:) > > On directory, one egg, please. Yeah, I totally agree: no directory in Chicken-eggs should have more than one egg. Alejo. http://azul.freaks-unidos.net/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Re: [Chicken-hackers] egg-post-commit
On 3/8/07, minh thu <[EMAIL PROTECTED]> wrote: What if the directory contains multiple eggs ? I ask this because I think I'll end up with lot of eggs for the gl-suite project. Is it better to have, gl-display-*, gl-font, gl-math, gl-repl, gl-samples, gl-etcaetera, or simply gl-suite ? (If the former, Felix, prepare to have more request from me:) On directory, one egg, please. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Re: [Chicken-hackers] egg-post-commit
2007/3/8, felix winkelmann <[EMAIL PROTECTED]>: On 3/7/07, Alejandro Forero Cuervo <[EMAIL PROTECTED]> wrote: > > egg-post-commit should only automatically upload an egg if (1) it > detects a change in the directory for the egg's latest release and (2) > the egg's directory doesn't have the 'autoupdate' Subversion property > set to 'no'. > > The directory for an egg's latest release would be: > > 1. If the egg has a 'tags' directory, > > 1.1. If the 'tags' directory has a 'latest' property set to 'foo', > the directory is 'tags/foo'. > > 1.2. Otherwise, the directory under 'tags' corresponding to the > greatest version number. > > 2. The egg's directory. > I'll do it exactly that way. Hi, What if the directory contains multiple eggs ? I ask this because I think I'll end up with lot of eggs for the gl-suite project. Is it better to have, gl-display-*, gl-font, gl-math, gl-repl, gl-samples, gl-etcaetera, or simply gl-suite ? (If the former, Felix, prepare to have more request from me:) Cheers, thu ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Re: [Chicken-hackers] egg-post-commit
On 3/8/07, Graham Fawcett <[EMAIL PROTECTED]> wrote: Out of curiosity --- if an egg doesn't have a 'tags' (and 'trunk') directory, it is possible to modify it so that it does? Yes, you can restructure your egg directory with "svn mv", for example. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Re: [Chicken-hackers] egg-post-commit
On 3/8/07, felix winkelmann <[EMAIL PROTECTED]> wrote: On 3/7/07, Alejandro Forero Cuervo <[EMAIL PROTECTED]> wrote: > > egg-post-commit should only automatically upload an egg if (1) it > detects a change in the directory for the egg's latest release and (2) > the egg's directory doesn't have the 'autoupdate' Subversion property > set to 'no'. > > The directory for an egg's latest release would be: > > 1. If the egg has a 'tags' directory, > [snip] I'll do it exactly that way. Out of curiosity --- if an egg doesn't have a 'tags' (and 'trunk') directory, it is possible to modify it so that it does? Thanks, Graham ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Re: [Chicken-hackers] egg-post-commit
On 3/7/07, Alejandro Forero Cuervo <[EMAIL PROTECTED]> wrote: egg-post-commit should only automatically upload an egg if (1) it detects a change in the directory for the egg's latest release and (2) the egg's directory doesn't have the 'autoupdate' Subversion property set to 'no'. The directory for an egg's latest release would be: 1. If the egg has a 'tags' directory, 1.1. If the 'tags' directory has a 'latest' property set to 'foo', the directory is 'tags/foo'. 1.2. Otherwise, the directory under 'tags' corresponding to the greatest version number. 2. The egg's directory. I'll do it exactly that way. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Re: [Chicken-hackers] egg-post-commit
> I think it would be preferable to use a tagged version. That way you can > commit as much as you wont and the auto-upload script will only > check the latest tagged version for changes. Yeah, I agree with this: egg-post-commit should only automatically upload an egg if (1) it detects a change in the directory for the egg's latest release and (2) the egg's directory doesn't have the 'autoupdate' Subversion property set to 'no'. The directory for an egg's latest release would be: 1. If the egg has a 'tags' directory, 1.1. If the 'tags' directory has a 'latest' property set to 'foo', the directory is 'tags/foo'. 1.2. Otherwise, the directory under 'tags' corresponding to the greatest version number. 2. The egg's directory. I would like to encourage egg authors to use the 'trunk', 'branches', 'tags' structure, I think it makes things easier. :-) Alejo. http://azul.freaks-unidos.net/ ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: Re : Re : [Chicken-users] Re: [Chicken-hackers] egg-post-commit
On 3/7/07, minh thu <[EMAIL PROTECTED]> wrote: 2007/3/7, felix winkelmann <[EMAIL PROTECTED]>: > On 3/7/07, minh thu <[EMAIL PROTECTED]> wrote: > > > > When you make a change, don't you up the version ? > > No. That's the job of the developer. I was talking a bout the developer when saying "you"... Ok, I understood "you" == "autocommit". > > > If it's the case, automatic upload would only involve new directory under > tags. > > > > Also, in the .meta file, maybe it would be wise to have an option to > > disable the .meta file. > > Good idea. So, this one means "don't run the script". Yep. > > >And an option to disable the .meta file after > > one run. > > I don't understand this one. Could you explain? And this one means "run it only once" then change the .meta file so it's disabled. I don't know if it would be really convenient but it allows the developer to set "run once", commit its changes and be sure that its changes are reflected, but also that it won't happen for the next changes. I think it would be preferable to use a tagged version. That way you can commit as much as you wont and the auto-upload script will only check the latest tagged version for changes. cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re : Re : [Chicken-users] Re: [Chicken-hackers] egg-post-commit
2007/3/7, felix winkelmann <[EMAIL PROTECTED]>: On 3/7/07, minh thu <[EMAIL PROTECTED]> wrote: > > When you make a change, don't you up the version ? No. That's the job of the developer. I was talking a bout the developer when saying "you"... > If it's the case, automatic upload would only involve new directory under tags. > > Also, in the .meta file, maybe it would be wise to have an option to > disable the .meta file. Good idea. So, this one means "don't run the script". >And an option to disable the .meta file after > one run. I don't understand this one. Could you explain? And this one means "run it only once" then change the .meta file so it's disabled. I don't know if it would be really convenient but it allows the developer to set "run once", commit its changes and be sure that its changes are reflected, but also that it won't happen for the next changes. Cheers, thu ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: Re : [Chicken-users] Re: [Chicken-hackers] egg-post-commit
On 3/7/07, minh thu <[EMAIL PROTECTED]> wrote: When you make a change, don't you up the version ? No. That's the job of the developer. If it's the case, automatic upload would only involve new directory under tags. Also, in the .meta file, maybe it would be wise to have an option to disable the .meta file. Good idea. And an option to disable the .meta file after one run. I don't understand this one. Could you explain? cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re : [Chicken-users] Re: [Chicken-hackers] egg-post-commit
2007/3/7, felix winkelmann <[EMAIL PROTECTED]>: On 3/6/07, Kon Lovett <[EMAIL PROTECTED]> wrote: > > > > BTW, shouldn't we really start thinking about automatic upload? > > Please, what does the above phrase mean? Automatic egg post when the > svn repo copy of the source is changed? I hope not. > Well, (un)fortunately, it means "yes". The problem is that it is gettting more and more involved having the proper setup for running egg-post-commit. Additionally I'd find it more convenient to have automatic uploads on commit since running the upload script manually can get tedious after a while. If you prefer to do it manually, I guess we should provide an option (as an svn property). So my proposal: - egg-post-commit can still be used as normal - if an egg has been changed by a commit, has a .meta file, all files listed in the .meta file are available and the directory does not have a "noautoupload" property (or whatever), then it is uploaded automatically to call/cc.org. Would that be acceptable? Hi, When you make a change, don't you up the version ? If it's the case, automatic upload would only involve new directory under tags. Also, in the .meta file, maybe it would be wise to have an option to disable the .meta file. And an option to disable the .meta file after one run. Cheers, thu ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Re: [Chicken-hackers] egg-post-commit
On 3/6/07, Kon Lovett <[EMAIL PROTECTED]> wrote: > > BTW, shouldn't we really start thinking about automatic upload? Please, what does the above phrase mean? Automatic egg post when the svn repo copy of the source is changed? I hope not. Well, (un)fortunately, it means "yes". The problem is that it is gettting more and more involved having the proper setup for running egg-post-commit. Additionally I'd find it more convenient to have automatic uploads on commit since running the upload script manually can get tedious after a while. If you prefer to do it manually, I guess we should provide an option (as an svn property). So my proposal: - egg-post-commit can still be used as normal - if an egg has been changed by a commit, has a .meta file, all files listed in the .meta file are available and the directory does not have a "noautoupload" property (or whatever), then it is uploaded automatically to call/cc.org. Would that be acceptable? cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Re: [Chicken-hackers] egg-post-commit
On Mar 6, 2007, at 2:24 AM, felix winkelmann wrote: Hi! I have made some modifications to egg-post-commit to properly handle tags in the wiki->html conversion. I'm still shaking with horror from the experience... getting the proper versions of the proper eggs installed and figured out how to load stream-wiki extensions was no fun at all... Anybody trying to use egg-post-commit should check that he has the proper eggs (and up-to-date versions) installed, specifically: syntax-case utils srfi-1 srfi-13 srfi-18 posix regex ftp http-client format url base64 svn-client html-stream stream-ext srfi-40 stream-wiki matchable Oh yes, GNU enscript must be installed of course, a recent version. BTW, shouldn't we really start thinking about automatic upload? Please, what does the above phrase mean? Automatic egg post when the svn repo copy of the source is changed? I hope not. If we can't do this via svn magic (or if it takes to long to set up), I have absolutely no problems running a cronjob that looks for changes and does the necessary upload once a day. In fact, I think this is probably the best way to go. Mario: would you assist me with that? thanks for your patience. cheers, felix ___ Chicken-hackers mailing list Chicken-hackers@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-hackers ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
