On Sun, 13 Apr 2014 18:12:05 +0200, Andy Bradford
<amb-fos...@bradfords.org> wrote:
Thus said Stephan Beal on Sun, 13 Apr 2014 17:54:49 +0200:
question: would this need fixing?
I think at the very least it should be possible to unset a user that was
configured as a default via ``fossil user default user''; perhaps a
``fossil user undefault'' which executes:
DELETE FROM vvar WHERE name = 'default-user'
yes, that what be good and more sensible than either to know about the
sqlite route (the user really shouldn't need to in my view) or
being required to close/through away .fslckout and re-open the repo.
only after your and stephan's responses I realize that `default-user' is
_not_ initialized at the time of repo creation/opening but
indeed only via `fossil user default somename'. in view of this fact its
confusing (I was) or even wrong that immediately after repo
creation and opening it, `fossil user default' lists the admin user:
either this needs to go away (empty response) or the default-user indeed
would have to be set at that point as if `fossil user default
name-of-admin-user' had been issued. is this correct?
Whether or not the bigger issue of handling default-user as a setting
should be tackled, that's a separate issue in my opinion, though perhaps
the interface should be unified. I started looking into it, but I'm not
sure where it will lead.
It does look like Fossil does have some support to use default-user as a
setting, but no interface short of sqlite3 to set it.
http://www.fossil-scm.org/index.html/artifact/58a793626f84fb38?ln=367,369
But I'm not sure what else will be impacted by enabling the setting, and
how it will play with other default-user sensitive settings.
Andy
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
