Re: [viewvc-users] When and why did "allow_tar" get pulled out?
Nico Kadel-Garcia <[email protected]>
| Newsgroups | gmane.comp.version-control.cvs.viewcvs.user |
|---|---|
| Message-ID | <ce6304781001290835p4ed0f93dkfb8f1752c3923e08__18728.5780128606$1264782929$gmane$org@mail.gmail.com> |
On Fri, Jan 29, 2010 at 9:28 AM, C. Michael Pilato <[email protected]> wrote: > Nico Kadel-Garcia wrote: >> I used to use "allow_tar" in viewvc-1.0.9 to allow tarball >> downloading, to avoid needing to install Subversion clients to access >> test tarballs. This was apparently yanked out at 1.1.0, although the >> help pages still reflect the presence of the "Download tarball" >> option. >> >> The consistent and confusing labeling of "allow_tar" versus its >> description as "Download tarball" in the documentation was a minor >> issue. But yanking out the utility without updating the documentation >> is... an unpleasant surprise. Why was it pulled? Would it be possible >> to have restored as an option? > > It wasn't pulled -- it was merely relocated. Rather than have allow_markup, > allow_tar and allow_annotate, plus the new allow_checkout and allow_roots > options needed, I unified these into a single new 'allowed_views' option in > the 1.1.0 line. That little tidbit didn't make it into the release notes, > but is noted in the "Upgrading from 1.0" portion of the "Upgrading HOW-TO" > doc[1]. *THANK* you. That makes sense. > (Heheh... I just noticed that the example immediately after that portion of > doc errantly still refers to the allow_tar configuration option. Sheesh.) > > As for the online help ... that stuff is atrociously out of date. I'd > welcome any suggestions you could offer on updating those docs (over on > [email protected], please). Thanks! I'll send a followup there, but I just started a new job, so I'm short on cycles myself to do it. ------------------------------------------------------ http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2443057 To unsubscribe from this discussion, e-mail: [[email protected]].