* Questions about Sourceware
@ 2017-03-09 15:14 Marian Csontos
2017-03-09 15:55 ` Frank Ch. Eigler
0 siblings, 1 reply; 3+ messages in thread
From: Marian Csontos @ 2017-03-09 15:14 UTC (permalink / raw)
To: Frank Eigler, overseers
Hi Frank, and overseers, I am still trying to find my way around on
sourceware to proceed with ikiwiki, and I have few questions, about your
preferred ways.
For each ikiwiki there will be needed:
2 public accessible group writable git repos - setup and content,
somewhere under $poject-home, linked from /git,...
How to create them?
- Ask overseers to have them created for us.
- Or create them and have them linked from /git, /git/SOURCEWARE-GITWEB,...;
...and optionally added to gitweb's project_list file?
- Is everything supposed to be there?
...and setfacl-ed...?
and a group writable setup and working directories.
These will be checked out from the above git repos. As generated
content, should this be under /sourceware/projects or is
there another preferred location?
And few more related questions:
Shall I send you script(s) for */sourceware/infra/bin/*?
...and if so, as ikiwiki's auto.setup is interactive, is command
line preferred, or is interactive accepted as well?
I already tweaked it a bit to ask more questions, and if we agree on
some standard locations, I can make it to ask less or none if possible.
May I ask, why sourceware does not use gitweb's automatic repo search?
Would it mean less work for you, if groups had group writable
directory under /git, /sourceware/www/sourceware/htdocs/git/,...?
Also structure under /git is mostly flat, is that strongly preferred
way? E.g. it does make scripts simpler - no need to handle directories
when linking.
Exception to the rule: cygwin-apps/.
Would group writable directories with repo search be useful and save you
some work?
-- Martian
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Questions about Sourceware
2017-03-09 15:14 Questions about Sourceware Marian Csontos
@ 2017-03-09 15:55 ` Frank Ch. Eigler
2017-03-09 17:31 ` Marian Csontos
0 siblings, 1 reply; 3+ messages in thread
From: Frank Ch. Eigler @ 2017-03-09 15:55 UTC (permalink / raw)
To: Marian Csontos; +Cc: Frank Eigler, overseers
Hi -
> [...]
> For each ikiwiki there will be needed:
> 2 public accessible group writable git repos - setup and content, somewhere
> under $poject-home, linked from /git,...
>
> How to create them?
> - Ask overseers to have them created for us.
^^ this.
> These will be checked out from the above git repos. As generated
> content, should this be under /sourceware/projects or is there
> another preferred location?
There will be a project home directory made for you.
> And few more related questions:
> Shall I send you script(s) for */sourceware/infra/bin/*?
> ...and if so, as ikiwiki's auto.setup is interactive, is command
> line preferred, or is interactive accepted as well?
Do these need to go into infra/bin? If they are for ikiwiki only,
you could put them under some /bin subtree of your own.
> [...]
> May I ask, why sourceware does not use gitweb's automatic repo search?
Not sure; maybe that wasn't available in the prehistoric versions when
we first set them up.
> Would it mean less work for you, if groups had group writable
> directory under /git, /sourceware/www/sourceware/htdocs/git/,...?
> [...]
It depends on how many such repos you will end up needing. If it's
just the one or two, don't worry about it; our symlink widgetry will
do. If it's a slew, then something like the cygwin-apps/ structure
will be needed.
- FChE
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Questions about Sourceware
2017-03-09 15:55 ` Frank Ch. Eigler
@ 2017-03-09 17:31 ` Marian Csontos
0 siblings, 0 replies; 3+ messages in thread
From: Marian Csontos @ 2017-03-09 17:31 UTC (permalink / raw)
To: Frank Ch. Eigler; +Cc: Frank Eigler, overseers
On 03/09/2017 04:55 PM, Frank Ch. Eigler wrote:
> Hi -
>
>> [...]
>> For each ikiwiki there will be needed:
>> 2 public accessible group writable git repos - setup and content, somewhere
>> under $poject-home, linked from /git,...
>>
>> How to create them?
>> - Ask overseers to have them created for us.
>
> ^^ this.
>
>> These will be checked out from the above git repos. As generated
>> content, should this be under /sourceware/projects or is there
>> another preferred location?
>
> There will be a project home directory made for you.
Is it /sourceware/projects/lvm2-home ?
Or more likely /sourceware/something-else/lvm2, which would make e.g.
rsync bit easier ?
Whatever, I can now start with scripting, and will update as we agree on
the final locations. Will push to a git repo too, so if there is anyone
setting another wiki, or cloning and contributing, it could be reused.
Thanks!
-- Martian
>
>
>> And few more related questions:
>> Shall I send you script(s) for */sourceware/infra/bin/*?
>> ...and if so, as ikiwiki's auto.setup is interactive, is command
>> line preferred, or is interactive accepted as well?
>
> Do these need to go into infra/bin? If they are for ikiwiki only,
> you could put them under some /bin subtree of your own.
>
>> [...]
>> May I ask, why sourceware does not use gitweb's automatic repo search?
>
> Not sure; maybe that wasn't available in the prehistoric versions when
> we first set them up.
>
>> Would it mean less work for you, if groups had group writable
>> directory under /git, /sourceware/www/sourceware/htdocs/git/,...?
>> [...]
>
> It depends on how many such repos you will end up needing. If it's
> just the one or two, don't worry about it; our symlink widgetry will
> do. If it's a slew, then something like the cygwin-apps/ structure
> will be needed.
>
>
> - FChE
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-03-09 17:31 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-09 15:14 Questions about Sourceware Marian Csontos
2017-03-09 15:55 ` Frank Ch. Eigler
2017-03-09 17:31 ` Marian Csontos
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).