Re: [fossil-users] Template repositories
On Fri, Dec 17, 2010 at 6:07 AM, Nolan Darilek no...@thewordnerd.infowrote: If so, I wonder if a variant of fossil new might accept a second repository file or URL argument. This would copy all artifacts from the second repository into the first, then set a new project ID on the first repository. This would ensure that each new project has a distinct ID from the template, but still starts with the same artifacts. You can achieve that by doing something like this (which would be easly scriptable): (PS: on my system 'f' is a symlink to fossil) f clone the_original newrepo.fsl mkdir newrepo cd newrepo f open ../newrepo.fsl f close # disassociates the files from the opened repo rm ../newrepo.fsl f new ../newrepo.fsl f open ../newrepo.fsl f add . f commit -m ... -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Template repositories
On Fri, Dec 17, 2010 at 12:07 AM, Nolan Darilek no...@thewordnerd.infowrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have some situations where I find myself creating the same starter projects over and over. For instance, I'll create the same starter web app with similar database setup and coding style. Were I doing this with Git, I'd start with a template repository, clone it and go. But I'm not sure this is possible with Fossil. My understanding is that Fossil creates a unique project ID such that it ensures syncs happen only between repositories of the same project. Is this accurate? If so, I wonder if a variant of fossil new might accept a second repository file or URL argument. This would copy all artifacts from the second repository into the first, then set a new project ID on the first repository. This would ensure that each new project has a distinct ID from the template, but still starts with the same artifacts. Or is there some other way to accomplish this goal? Just make a copy of the template repository. If you want to change the project id you can do that using: fossil test-detach copied-repo.fossil If you don't like using a test command in Fossil, you can do the same in SQLite: sqlite3 copied-repo.fossil UPDATE config SET value=lower(hex(randomblob(20))) WHERE value='project-code' -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0K8AwACgkQIaMjFWMehWKbdACfZL2dpYkdcExmsBrq2COB/rDC uScAn1jwlg8weJmPAd5jjPKTE3dh4Pid =pyMJ -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Template repositories
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks, glad to know this is possible. Should I open a ticket for the proposed new behavior for fossil new? I know of several projects that use this Git repository method to jumpstart new projects/web apps based on them, so it's definitely not unheard of. Basically, fossil new myproject.fossil http://my.fossil.server/template; would first run a clone, then swap out the project-code with a new random value. In any case, thanks for the test command. On 12/17/2010 06:20 AM, Richard Hipp wrote: On Fri, Dec 17, 2010 at 12:07 AM, Nolan Darilek no...@thewordnerd.infowrote: I have some situations where I find myself creating the same starter projects over and over. For instance, I'll create the same starter web app with similar database setup and coding style. Were I doing this with Git, I'd start with a template repository, clone it and go. But I'm not sure this is possible with Fossil. My understanding is that Fossil creates a unique project ID such that it ensures syncs happen only between repositories of the same project. Is this accurate? If so, I wonder if a variant of fossil new might accept a second repository file or URL argument. This would copy all artifacts from the second repository into the first, then set a new project ID on the first repository. This would ensure that each new project has a distinct ID from the template, but still starts with the same artifacts. Or is there some other way to accomplish this goal? Just make a copy of the template repository. If you want to change the project id you can do that using: fossil test-detach copied-repo.fossil If you don't like using a test command in Fossil, you can do the same in SQLite: sqlite3 copied-repo.fossil UPDATE config SET value=lower(hex(randomblob(20))) WHERE value='project-code' ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0Lj9MACgkQIaMjFWMehWLHgwCdGk3rgVIIGUWSqgWIPgmgackt OecAmwUXoJ3EvxTeojEHsf9xCGuGimbA =3zbf -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
