Re: [fossil-users] Zipping a packaged release -- option to ignore specific folder?
On May 26, 2011, at 19:08 , Stephan Beal wrote: On Thu, May 26, 2011 at 7:03 PM, Richard Hipp d...@sqlite.org wrote: Exactly. I think it best that this not be a persistent setting, but just a command-line option or query parameter. Or possibly a propagating tag? That would(?) solve the branching/timeframe issue, i think, by simply taking the latest value (for a given revision) of the tag's value. ++ But I still believe, that the true problem is storing in the repository things that are not part of the project... Kind regards, Remigiusz Modrzejewski ___ 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] Zipping a packaged release -- option to ignore specific folder?
On Mon, May 30, 2011 at 3:43 AM, Remigiusz Modrzejewski l...@maxnet.org.pl wrote: But I still believe, that the true problem is storing in the repository things that are not part of the project... He did not say they were not part of the project. But anyway, maybe this optional part of the project could be handled as a sub-project with its own repository. ___ 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] Zipping a packaged release -- option to ignore specific folder?
I'm thinking specifically about things like JavaScript that makes the web ui slightly nicer (diff coloring / source coloring). So they are not part of the project (and shouldn't be exported for, say, a C# based project), but need to be part of the repository so that all of the formatting carries with the repo. Unless I'm missing an easier way to deal with that? Tomek On Mon, May 30, 2011 at 10:25 AM, Ron Wilson ronw.m...@gmail.com wrote: On Mon, May 30, 2011 at 3:43 AM, Remigiusz Modrzejewski l...@maxnet.org.pl wrote: But I still believe, that the true problem is storing in the repository things that are not part of the project... He did not say they were not part of the project. But anyway, maybe this optional part of the project could be handled as a sub-project with its own repository. ___ 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
Re: [fossil-users] Zipping a packaged release -- option to ignore specific folder?
On 5/30/2011 10:46 AM, Tomek Kott wrote: I'm thinking specifically about things like JavaScript that makes the web ui slightly nicer (diff coloring / source coloring). Unless I'm missing an easier way to deal with that? If it works for your project, you could keep your fossil UI tweaks available on a webserver somewhere, and your fossil templates could simply refer to them by fully qualified URL. The niceties would be missing when you're offline, of course, but personally I'd rather have that than fossil ui support files in my project. -- Joshua Paine LetterBlock: Web Applications Built With Joy http://letterblock.com/ 301-576-1920 ___ 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] Zipping a packaged release -- option to ignore specific folder?
True, and I do have a website, but to me that kind of ruins the whole self-contained nature of Fossil which I love... On Mon, May 30, 2011 at 11:05 AM, Joshua Paine jos...@letterblock.comwrote: On 5/30/2011 10:46 AM, Tomek Kott wrote: I'm thinking specifically about things like JavaScript that makes the web ui slightly nicer (diff coloring / source coloring). Unless I'm missing an easier way to deal with that? If it works for your project, you could keep your fossil UI tweaks available on a webserver somewhere, and your fossil templates could simply refer to them by fully qualified URL. The niceties would be missing when you're offline, of course, but personally I'd rather have that than fossil ui support files in my project. -- Joshua Paine LetterBlock: Web Applications Built With Joy http://letterblock.com/ 301-576-1920 ___ 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
Re: [fossil-users] Zipping a packaged release -- option to ignore specific folder?
On 5/30/2011 11:25 AM, Tomek Kott wrote: True, and I do have a website, but to me that kind of ruins the whole self-contained nature of Fossil which I love... Once you have a dozen or more fossil repos, though, it just gets silly to duplicate SCM ui code in each of them. -- Joshua Paine LetterBlock: Web Applications Built With Joy http://letterblock.com/ 301-576-1920 ___ 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] Zipping a packaged release -- option to ignore specific folder?
The ZIP and tarball generators built into Fossil are not intended to be a delivery mechanism for product releases. They are simply a convenient way of downloading a particular version of your project without having to clone the whole repo. And for that purpose, the ZIP and tarballs should contain all source files in the repo - including JS and other UI stuff. If you want to make ZIP or tarball releases that contain a subset of files, that's fine. Nothing wrong with that. Maybe those release ZIPs and tarballs also contain precompiled binaries and other files that are not found in the repository too. I think this whole discussion comes down to people trying to use the ZIP and tarball generators as a release mechanism when in fact that is not what they are. Now if you want to argue that there should be some sort of separate ZIP/tarball generator for releases, and put in a feature request for the same, that is an entirely different matter. Your enhancement request will be given due consideration. But I think trying to shoehorn the existing version ZIP/tarball mechanism into providing release ZIP/tarballs is the wrong approach. -- 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
