[fossil-users] Sub-repositories?
I just saw an intriguing message in the timeline. "Leaf: Merge the sub-repo capability into trunk." I can't find anywhere in the help, the fossil docs nor in the wiki that talks about this. How does one use this new sub-repo capability? -- "Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot." --Sergey Brin, demonstrating the emptiness of the "don't be evil" mantra. ___ 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] Sub-repositories?
More important, what *are* subrepositories? Entirely separate fossils linked to the main repository, or separate namespaces for tags and such in a single fossil? Or the ability to open a nested repository in another? Wondering if I'll need to migrate some of my multi-repository fossils to a new format somehow. On 03/28/2011 09:36 PM, Michael Richter wrote: > I just saw an intriguing message in the timeline. "Leaf: Merge the sub-repo > capability into trunk." I can't find anywhere in the help, the fossil docs > nor in the wiki that talks about this. How does one use this new sub-repo > capability? > > > > > ___ > 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] Sub-repositories?
On Mon, Mar 28, 2011 at 10:37 PM, Nolan Darilek wrote: > More important, what *are* subrepositories? Entirely separate fossils > linked to the main repository, or separate namespaces for tags and such > in a single fossil? Or the ability to open a nested repository in another? > > Wondering if I'll need to migrate some of my multi-repository fossils to > a new format somehow. > > > On 03/28/2011 09:36 PM, Michael Richter wrote: > > I just saw an intriguing message in the timeline. "Leaf: Merge the > sub-repo > > capability into trunk." I can't find anywhere in the help, the fossil > docs > > nor in the wiki that talks about this. How does one use this new > sub-repo > > capability? > Here's my conjecture, based on how Git does submodules, without having looked at the Fossil subrepository code... I'm guessing that in the repository, a submodule might be represented by an artifact that contains an identification of the subrepository, plus the identifier of the checked-out tree for that repository, with a path in a manifest identifying the location of the subrepository in the directory tree. A subrepository could be identified by a Fossil URL or maybe requiring it to be a sibling of the current repository -- a URL is nice, because it provides a way to retrieve it when you clone the parent repository. On disk, a subrepository might be checked-out as a subdirectory of the current check-out (corresponding to the entry in the manifest). Bill ___ 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] Sub-repositories?
On Mon, Mar 28, 2011 at 10:36 PM, Michael Richter wrote:
> I just saw an intriguing message in the timeline. "Leaf: Merge the
> sub-repo capability into trunk." I can't find anywhere in the help, the
> fossil docs nor in the wiki that talks about this. How does one use this
> new sub-repo capability?
>
Sub-repositories is nothing more than the opportunity to create
single-signon for two or more separate repositories at a single website.
We have an SQLite Consortium member who is using several proprietary SQLite
extensions. Previously, they had a separate login for the repository of
each extension. Password management was becoming an issue for them, so they
requested a unified private website, with a wiki, that gives them access to
all of the extensions all at once. Subrepositories provide this.
Suppose the subrepos are named abc.fossil, def.fossil, and ghi.fossil. The
name of the main repository is xyz.fossil. All the repositories files live
in the same directory, say. Suppose the xyz.fossil repository is accessible
as: https://domain/path/to/xyz. Then you create entries in the xyz.fossil
SQLite database like this:
INSERT INTO config(name,value) VALUES('subrepo:abc','user1:abc.fossil');
INSERT INTO config(name,value) VALUES('subrepo:def','user2:def.fossil');
INSERT INTO config(name,value)
VALUES('subrepo.lmnop','user3:ghi.fossil');
Those entries activate subrepositories so that users can log once to xyz but
access the other repositories using URLs like:
https://domain/path/to/xyz/abc/timeline
https://domain/path/to/xyz/def/timeline
https://domain/path/to/xyz/lmnop/timeline
The access permissions to the subrepositories are those for user1, user2,
and user3, respectively.
The client company has many individuals at several office locations who all
need access to the subrepositories. But on the subrepos for the proprietary
SQLite extensions, we only have a single login for the client as a whole.
The subrepo mechanism allows the various users at the client company to each
have their own username and password but still share access to the subrepos
using a unified login name.
We only allow the client "Reader" capabilities when accessing the subrepos.
But for the main repo that contains the project wiki and other resources,
the client has full "Setup" capability so that they can do whatever they
want on their private repo without accidentally making undesirable changes
to the subrepos.
>
> --
> "Perhaps people don't believe this, but throughout all of the discussions
> of entering China our focus has really been what's best for the Chinese
> people. It's not been about our revenue or profit or whatnot."
> --Sergey Brin, demonstrating the emptiness of the "don't be evil" mantra.
>
> ___
> 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] Sub-repositories?
Thanks, Richard. That cleared things up. On 29 March 2011 20:25, Richard Hipp wrote: -- "Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot." --Sergey Brin, demonstrating the emptiness of the "don't be evil" mantra. ___ 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] Sub-repositories?
So it sounds like this might be a way to support the use case for which I proposed index.fossil last week, correct? That is, I could have a default repository served up at the root of the domain, with the wiki and other links referencing its pages, but add sub-repositories for the various spin-off projects. Is this accurate? On 03/29/2011 10:45 AM, Michael Richter wrote: > Thanks, Richard. That cleared things up. > > On 29 March 2011 20:25, Richard Hipp wrote: > > > > > > > ___ > 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] Sub-repositories?
On Tue, Mar 29, 2011 at 8:25 AM, Richard Hipp wrote: > We only allow the client "Reader" capabilities when accessing the subrepos. > But for the main repo that contains the project wiki and other resources, > the client has full "Setup" capability so that they can do whatever they > want on their private repo without accidentally making undesirable changes > to the subrepos. Does that mean that users authorized to commit changes to the subrepos must login directly to the respective subrepo? Does that also require a seperate user ID from the single-sign-on ID? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
