On 9/15/2015 6:09 PM, Ron W wrote:
On Tue, Sep 15, 2015 at 6:18 PM, The Tick <[email protected]
<mailto:[email protected]>> wrote:
However, if I do that, then the image would be included in the
project download, right? I guess one small image would not be that
big a deal, but it would be good to not foist unnecessary files on
users.
What about your project's "user manual"? Screenshots are often included,
so would be reasonable to include in the source "tarball".
First of all, thanks for your reply.
The app is a Tcl script and associated image files. There is no "User
Manual". It also requires Tcl with the Tk Img package be installed. If
someone does not know how to unpack a ZIP and double-click a file,
well... Adding a windows installer (even NullSoft) would add more
complexity than I am willing to handle, especially trying to determine
if Tcl is already installed, downloading ActiveState's version if not,
etc. I am also assuming Unix users know how to unpack a tarball.
There's an 'INSTALL.txt' that should provide enough information. After
that I will assume that most people know how to click a mouse.
If the 'INSTALL.txt' is unclear or there are bugs, I'd like the bug
tracking system to be easy to use. Since there's no "Users Manual", I do
not need nor want a public "wiki".
FYI, Fossil can automatically create "tarballs" of the files in the
repository for a specified version, which defaults to the latest.
That is one of the features that I was looking for. How to get the URL
for that to put on the 'home' page is one of my next tasks. I doubt that
most windows users would explore fossil's interface (and understand it
enough) to click 'files' then click the weird check-in id to get to the
ZIP download button. At this point I'm assuming I can just copy that URL
and duplicate it on my home page.
I suppose a work-around would be to add the image(s) to a specific
version of your project, commit that version, then remove (rm) the
image(s) from the next version and commit that. Then your pages can link
to the image(s) at that specific version of your project, while the
automatically made tarballs would not have it/them.
I'll have to explore that. It's just one image to get an idea of the
app's GUI.
Also, besides Fossil created tarballs, your project's build procedure
can, possibly should, create release packages. Such packages would
contain only what you choose to put in them. (But, see below.) The
specific version "trick" I described would work for these, as well as
images.
Since there is no build procedure, I want whatever source control system
or host to supply the simple download Zip/Tar button. Again, thanks for
your help.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
