{"thread":{"id":"21177","subject":"gitweb - bare repos integration - owner info in description file","startedAt":"2009-10-09T20:50:00Z","lastAt":"2009-11-04T23:48:21Z","messageCount":11,"participants":["Eugene Sajine","Jakub Narebski","Johannes Schindelin","Miklos Vajna","Petr Baudis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"124528","messageId":"76c5b8580910091350o5cd90d3dobe2a21c18fa56dfd@mail.gmail.com","threadId":"21177","inReplyTo":null,"subject":"gitweb - bare repos integration - owner info in description file","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2009-10-09T20:50:00Z","receivedAt":"2009-10-09T20:50:00Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":"Hi,\n\nHere is another issue with gitweb integration which i think might be\nconsidered as a feature proposal:\n\nI have a central place where bare repos are. They're owned by the user\nunder which we are serving them, let's say “git”. So, gitweb is going\nto show me\n\nRepo1 owner git etc…\n\nIn order to show a real owner I have to rebuild gitweb.cgi, to tell it\nto use the file for GITWEB_LIST and edit the file… In fact I think\ngitweb shouldn’t carry this info, but bare repos should.\n\nSo my idea is:\n\nEither provide a key to\n$ git clone –bare –u “owner/email”\n\nor take the user.email parameter from .gitconfig.\n\nin both cases the info can go to description file of bare repo, so it\ncan look like:\n\n$owner=owner@server.com\n\n$description=”very long description”\n\nOr in xml form…\n\n\nYes, description file might become a bit more complicated in its\nlayout. But, the benefits are obvious:\n\n- No need to support multiple lists/files\n- Bare repo carries all info about itself (together with –d feature I\ndescribed earlier).\n\nI this circumstances gitweb’s GITWEB_LIST will be only filter (only\nrepo path is necessary to show/not show), and it seems that narrowed\nfunctionality here is a good thing...\n\nYour thoughts?\n\nThanks,\nEugene\n"},{"id":"124537","messageId":"m3ab00gr25.fsf@localhost.localdomain","threadId":"21177","inReplyTo":"76c5b8580910091350o5cd90d3dobe2a21c18fa56dfd@mail.gmail.com","subject":"Re: gitweb - bare repos integration - owner info in description file","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2009-10-09T22:07:00Z","receivedAt":"2009-10-09T22:07:00Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Eugene Sajine <euguess@gmail.com> writes:\n\n> Here is another issue with gitweb integration which i think might be\n> considered as a feature proposal:\n> \n> I have a central place where bare repos are. They're owned by the user\n> under which we are serving them, let's say “git”. So, gitweb is going\n> to show me\n> \n> Repo1 owner git etc…\n> \n> In order to show a real owner I have to rebuild gitweb.cgi, to tell it\n> to use the file for GITWEB_LIST and edit the file… In fact I think\n> gitweb shouldn’t carry this info, but bare repos should.\n\nIt is not gitweb that carries this info, but file with list of\nrepositories (GITWEB_LIST).  And you can pre-generate this file using\ngitweb.\n\n> \n> So my idea is:\n> \n> Either provide a key to\n> $ git clone –bare –u “owner/email”\n> \n> or take the user.email parameter from .gitconfig.\n> \n> in both cases the info can go to description file of bare repo, so it\n> can look like:\n> \n> $owner=owner@server.com\n> \n> $description=”very long description”\n\nRTFM (in this case gitweb/README).  gitweb.owner and gitweb.description\nconfiguration variables in per-repository config.\n\n> \n> Or in xml form…\n\nAaaaaaaaaaaaaaaaaaaaaaaa...\n\n%\n\"To be fair, there are uses for XML. On Halloween, for example.\"\n\n     - Johannes Schindelin, on git@vger.kernel.org\n%\n> \n> \n> Yes, description file might become a bit more complicated in its\n> layout. But, the benefits are obvious:\n> \n> - No need to support multiple lists/files\n> - Bare repo carries all info about itself (together with –d feature I\n> described earlier).\n> \n> I this circumstances gitweb’s GITWEB_LIST will be only filter (only\n> repo path is necessary to show/not show), and it seems that narrowed\n> functionality here is a good thing...\n\nGITWEB_LIST is meant for the case when you want to avoid scanning\nfilesystem for git repositories.  And you can filter out repositories\nwithout using GITWEB_LIST (see documentation).\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"124539","messageId":"76c5b8580910091532yd6c6fc4ib942a29c827f3a6c@mail.gmail.com","threadId":"21177","inReplyTo":"m3ab00gr25.fsf@localhost.localdomain","subject":"Re: gitweb - bare repos integration - owner info in description file","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2009-10-09T22:32:25Z","receivedAt":"2009-10-09T22:32:25Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":">\n> RTFM (in this case gitweb/README).  gitweb.owner and gitweb.description\n> configuration variables in per-repository config.\n>\n\nOk, my bad, didn't get there;)It is good to know there are places\nwhere to keep the info. But it is not the point. The point is to\nintegrate gitweb with bare repo creation more than it is right now by\nproviding keys which will help filling out this info at the bare repo\ncreation stage.\n\nshortly i'm talking about command like this (the key names are for sample only):\n\n$ git clone --bare repo repo.git -desc \"description\" -gwowner\n\"gitwebowner@server.com\" -cloneurl \"git://host/repo.git\"\n\nseems to me quite comfy, and no headache...\n\n\n> %\n> \"To be fair, there are uses for XML. On Halloween, for example.\"\n>\n>     - Johannes Schindelin, on git@vger.kernel.org\n> %\n\nyeah, to show kids xml print outs as an answer to \"trick or treat!\".\nCan save on candies;)\n\nThanks,\nEugene\n"},{"id":"124582","messageId":"200910102045.13374.jnareb@gmail.com","threadId":"21177","inReplyTo":"76c5b8580910091532yd6c6fc4ib942a29c827f3a6c@mail.gmail.com","subject":"Re: gitweb - bare repos integration - owner info in description file","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2009-10-10T18:45:11Z","receivedAt":"2009-10-10T18:45:11Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"On Sat, 10 Oct 2009, Eugene Sajine wrote:\n> >\n> > RTFM (in this case gitweb/README).  gitweb.owner and gitweb.description\n> > configuration variables in per-repository config.\n> \n> Ok, my bad, didn't get there;) It is good to know there are places\n> where to keep the info. But it is not the point. The point is to\n> integrate gitweb with bare repo creation more than it is right now by\n> providing keys which will help filling out this info at the bare repo\n> creation stage.\n> \n> shortly i'm talking about command like this (the key names are for sample only):\n> \n> $ git clone --bare repo repo.git -desc \"description\" -gwowner\n> \"gitwebowner@server.com\" -cloneurl \"git://host/repo.git\"\n> \n> seems to me quite comfy, and no headache...\n\nThe project description, project owner and (clone) url are used by \ngitweb only, so I don't see why git-clone has to feature-creep to\nset them.\n\n[cut off part about using XML for all of gitweb config: description,\n owner, cloneurl]\n> > %\n> > \"To be fair, there are uses for XML. On Halloween, for example.\"\n> >\n> >     - Johannes Schindelin, on git@vger.kernel.org\n> > %\n> \n> yeah, to show kids xml print outs as an answer to \"trick or treat!\".\n> Can save on candies;)\n\nErr, I think Dscho meant here that XML is so *scary*... Isn't it?\n\n-- \nJakub Narebski\nPoland\n"},{"id":"124585","messageId":"76c5b8580910101845h43a607f0sd4184da302a19963@mail.gmail.com","threadId":"21177","inReplyTo":"200910102045.13374.jnareb@gmail.com","subject":"Re: gitweb - bare repos integration - owner info in description file","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2009-10-11T01:45:06Z","receivedAt":"2009-10-11T01:45:06Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":">\n> The project description, project owner and (clone) url are used by\n> gitweb only, so I don't see why git-clone has to feature-creep to\n> set them.\n>\n\n\nWell my logic is simple. Gitweb is a part of git bundle. If you don't\nwant to use gitweb you're free to use git clone as you want. I don't\nsee  why not to provide some usability features to it. For me it is\nquite obvious that it will be more comfortable to setup gitweb if this\nwould be in  place. Instead of putting info in few different places\nmanually, why not to give people a possibilty to do that using one\ncommand?\n\nThis is usability feature, but i feel that for me as a person who will\nsupport big ceantral bare repo hosting server, this would save huge\ntime and efforts...\n\nThanks,\nEugene\n"},{"id":"124599","messageId":"200910111239.15403.jnareb@gmail.com","threadId":"21177","inReplyTo":"76c5b8580910101845h43a607f0sd4184da302a19963@mail.gmail.com","subject":"Re: gitweb - bare repos integration - owner info in description file","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2009-10-11T10:39:14Z","receivedAt":"2009-10-11T10:39:14Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"On Sun, 11 Oct 2009, Eugene Sajine wrote:\n> >\n> > The project description, project owner and (clone) url are used by\n> > gitweb only, so I don't see why git-clone has to feature-creep to\n> > set them.\n> \n> Well my logic is simple. Gitweb is a part of git bundle. If you don't\n> want to use gitweb you're free to use git clone as you want. I don't\n> see  why not to provide some usability features to it. For me it is\n> quite obvious that it will be more comfortable to setup gitweb if this\n> would be in  place. Instead of putting info in few different places\n> manually, why not to give people a possibilty to do that using one\n> command?\n> \n> This is usability feature, but i feel that for me as a person who will\n> support big ceantral bare repo hosting server, this would save huge\n> time and efforts...\n\nAnd this would be best left for a custom script creating repositories\nand their git hosting related configuration.  Such script of necessity\nwould have to be site-specific, or at least contain site-specific \nconfiguration, like:\n * whether to use gitweb.owner or filesystem uid + GECOS is enough\n * whether to use gitweb.description or description file\n * whether to use gitweb.url, cloneurl file, or let gitweb autogenerate\n   clone / fetch URL from base URL\n * gitosis / gitlite configuration, if needed, or setup of public keys\n   for SSH authentication\n * project README.html file, if used\netc. \n\ngit-clone is not a dumping ground (also, code speak louder than words).\n\nI even think it might be mistake to have default 'description' file in \ntemplates...\n\n-- \nJakub Narebski\nPoland\n"},{"id":"124650","messageId":"alpine.DEB.1.00.0910120201350.4985@pacific.mpi-cbg.de","threadId":"21177","inReplyTo":"200910102045.13374.jnareb@gmail.com","subject":"Re: gitweb - bare repos integration - owner info in description file","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2009-10-12T00:04:46Z","receivedAt":"2009-10-12T00:04:46Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 10 Oct 2009, Jakub Narebski wrote:\n\n> On Sat, 10 Oct 2009, Eugene Sajine wrote:\n>\n> > [something, but forgot to say whom he quoted:]\n>\n> > > %\n> > > \"To be fair, there are uses for XML. On Halloween, for example.\"\n> > >\n> > >     - Johannes Schindelin, on git@vger.kernel.org\n> > > %\n> > \n> > yeah, to show kids xml print outs as an answer to \"trick or treat!\".\n> > Can save on candies;)\n> \n> Err, I think Dscho meant here that XML is so *scary*... Isn't it?\n\nXML can be scary.  Somebody on usenet once said something like: \"XML is \njust a skeleton; if you see a skeleton walking around, wouldn't you \nbe scared?\"\n\nWhat is really scary, though, is how many people really believe that just \nusing XML will magically solve all problems of this world.  They really \nbelieve that.\n\nCiao,\nDscho\n\n"},{"id":"124765","messageId":"76c5b8580910121448q67edd935wb189c8a6f9af2f2e@mail.gmail.com","threadId":"21177","inReplyTo":"alpine.DEB.1.00.0910120201350.4985@pacific.mpi-cbg.de","subject":"Re: gitweb - bare repos integration - owner info in description file","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2009-10-12T21:48:14Z","receivedAt":"2009-10-12T21:48:14Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":"Hi,\n\nSomebody from development camp recently complained here that there is\nno many end users \"chiming\" about issues in the mailing list. Well,\ndon't tell i didn't try;)\n\nFirst I tried to use gitweb.url, gitweb.description and gitweb.owner\nfiles and none of them worked... gitweb is unable to pickup the info\nfrom those files.\n\nAlthough it successfully interactively picks up info from description\nand cloneurl files. I didn't find a substitution for gitweb.owner...\n\nI might be sent to RTFM again, but i would like to bring an attention\nto the fact that setting up bare repo with these simplest parameters\nas well as setting up gitweb is a USABILITY NIGHTMARE for beginners. I\nwould even say more: while gitweb is very flexible and powerful, all\nits flexibility and power is hidden behind unusable management\ninterface, which IMHO requires a lot of improvements . Rebuilding to\nconfigure? Perl look-and-feel for configuration variables? I think\nthis is not the way to configure web applications no matter how smart\nand flexible application should be. There are some problems with XML,\nI don't care. Let's use simple property file. 1 property file! and let\ngitweb read it. don;t like this solution, propose yours..\n\nBut leaving the emotions aside and once again -\n\nOn Sun, 11 Oct 2009, Jakub Narebski wrote:\n\n>And this would be best left for a custom script creating repositories\n>and their git hosting related configuration.  Such script of necessity\n>would have to be site-specific, or at least contain site-specific\n>configuration, like:\n >* whether to use gitweb.owner or filesystem uid + GECOS is enough\n >* whether to use gitweb.description or description file\n >* whether to use gitweb.url, cloneurl file, or let gitweb autogenerate\n  >clone / fetch URL from base URL\n\nI don't get it. I'm talking specifically about gitweb bundled into git\npackage by default. It was bundled as i understand to provide full\nsolution (I don't see any other reason). What the heck is wrong with\ncontinuing to move in this direction? I'm not talking about to enforce\ngitweb usage, but just simplify the setup and configuration of a tool\nprovided by default...\nIf the user chooses default solution, what is wrong with providing\nsome usable way of doing things?\nDon't want to use git clone, fine. But, please, please save me from\nrebuilding gitweb, creating manually those files and putting info\ninside... It is 21st century or what?;)\n\n\n >* gitosis / gitlite configuration, if needed, or setup of public keys\n  >for SSH authentication\n\nAre they included into git bundle? I didn't see those tools there...\n\n >* project README.html file, if used\n>etc.\n\nYes, I might be stubborn, but is just because i feel that i can\ncontribute into making git better, although I'm not a developer. And i\nthink usability is the thing which all beginners would thank you\nfor... i understand that this issue is not the end of the world and i\nwill finally overcome the burden, i will develop my script and stuff,\nI hope somebody would support me in this:)\n\nThanks,\nEugene\n"},{"id":"124774","messageId":"20091012231928.GU23777@genesis.frugalware.org","threadId":"21177","inReplyTo":"76c5b8580910121448q67edd935wb189c8a6f9af2f2e@mail.gmail.com","subject":"Re: gitweb - bare repos integration - owner info in description file","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2009-10-12T23:19:28Z","receivedAt":"2009-10-12T23:19:28Z","isPatch":false,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Mon, Oct 12, 2009 at 05:48:14PM -0400, Eugene Sajine <euguess@gmail.com> wrote:\n> Yes, I might be stubborn, but is just because i feel that i can\n> contribute into making git better, although I'm not a developer.\n\nIn a distrubuted environment, there is no need to define who is a\ndeveloper and who is not. And contributing is allowed to anyone as long\nas you sign the Develoer's Certificate of Origin. :)\n\n(See\nhttp://repo.or.cz/w/git.git?a=blob;f=Documentation/SubmittingPatches;hb=HEAD)\n"},{"id":"126670","messageId":"20091103202211.GA17748@machine.or.cz","threadId":"21177","inReplyTo":"76c5b8580910121448q67edd935wb189c8a6f9af2f2e@mail.gmail.com","subject":"Re: gitweb - bare repos integration - owner info in description file","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2009-11-03T20:22:11Z","receivedAt":"2009-11-03T20:22:11Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"On Mon, Oct 12, 2009 at 05:48:14PM -0400, Eugene Sajine wrote:\n> Hi,\n> \n> Somebody from development camp recently complained here that there is\n> no many end users \"chiming\" about issues in the mailing list. Well,\n> don't tell i didn't try;)\n> \n> First I tried to use gitweb.url, gitweb.description and gitweb.owner\n> files and none of them worked... gitweb is unable to pickup the info\n> from those files.\n> \n> Although it successfully interactively picks up info from description\n> and cloneurl files. I didn't find a substitution for gitweb.owner...\n> \n> I might be sent to RTFM again, but i would like to bring an attention\n> to the fact that setting up bare repo with these simplest parameters\n> as well as setting up gitweb is a USABILITY NIGHTMARE for beginners. I\n> would even say more: while gitweb is very flexible and powerful, all\n> its flexibility and power is hidden behind unusable management\n> interface, which IMHO requires a lot of improvements . Rebuilding to\n> configure? Perl look-and-feel for configuration variables? I think\n> this is not the way to configure web applications no matter how smart\n> and flexible application should be. There are some problems with XML,\n> I don't care. Let's use simple property file. 1 property file! and let\n> gitweb read it. don;t like this solution, propose yours..\n\nI think you got confused by perhaps unclear gitweb/README wording. There\nis a single property file, it's called \"config\" and _that's_ where you\nset the gitweb configuration variables, in its gitweb section.\n\nTry running\n\n\tgit config gitweb.owner \"Eugene Sajine\"\n\tgit config gitweb.description tralala\n\nwithin the repository (and optionally marveling at the config file again\nafterwards). Is this what you are after?\n\nPerhaps the gitweb/README file doesn't make it clear enough that these\nare gitweb configuration variables, not stand-alone files, and maybe it\nshould provide an example on how to set them. I'm sure that if you will\nsubmit a patch for gitweb/README clarifying this, it will be welcome.\n\nKind regards,\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nA lot of people have my books on their bookshelves.\nThat's the problem, they need to read them. -- Don Knuth\n"},{"id":"126852","messageId":"76c5b8580911041548p74bf0f34o9fc4f1ab65307e72@mail.gmail.com","threadId":"21177","inReplyTo":"20091103202211.GA17748@machine.or.cz","subject":"Re: gitweb - bare repos integration - owner info in description file","fromName":"Eugene Sajine","fromEmail":"euguess@gmail.com","sentAt":"2009-11-04T23:48:21Z","receivedAt":"2009-11-04T23:48:21Z","isPatch":false,"sender":{"key":"euguess@gmail.com","avatar":null},"body":">\n> I think you got confused by perhaps unclear gitweb/README wording. There\n> is a single property file, it's called \"config\" and _that's_ where you\n> set the gitweb configuration variables, in its gitweb section.\n>\n> Try running\n>\n>        git config gitweb.owner \"Eugene Sajine\"\n>        git config gitweb.description tralala\n>\n> within the repository (and optionally marveling at the config file again\n> afterwards). Is this what you are after?\n>\n> Perhaps the gitweb/README file doesn't make it clear enough that these\n> are gitweb configuration variables, not stand-alone files, and maybe it\n> should provide an example on how to set them. I'm sure that if you will\n> submit a patch for gitweb/README clarifying this, it will be welcome.\n>\n> Kind regards,\n>\n> --\n>                                Petr \"Pasky\" Baudis\n> A lot of people have my books on their bookshelves.\n> That's the problem, they need to read them. -- Don Knuth\n>\n\nThank you for the advice, but I found a better solution than gitweb - cgit!\n\nI should say cgit is an amazing tool - nice design and graphic\nappearance, easy to set up and very easy to maintain, full of features\nand fits our environment nicely. Many thanks to the Author (Lars\nHjemli) and all contributors!\n\nEugene\n"}]}