| 1 |
Petteri Räty wrote: |
| 2 |
>> Please note, I'm not talking about applications like portage or pkgcore, |
| 3 |
>> just the ebuild text files, which I understand have one maintainer? |
| 4 |
> |
| 5 |
> Many ebuilds are in maintained by a bunch of people via herds. |
| 6 |
> |
| 7 |
That's not really an issue for a db app. |
| 8 |
|
| 9 |
>> I appreciate that source control is needed to maintain files over a |
| 10 |
>> period of time and to roll back changes. Does that happen with ebuilds? |
| 11 |
>> |
| 12 |
> Rolling back changes does not happen that often but a history is useful. |
| 13 |
> |
| 14 |
Sure, that's why I mentioned having a svn backend if an archive table is not |
| 15 |
considered acceptable. |
| 16 |
|
| 17 |
>> I'm thinking in any case that a db app can save old revisions or use a |
| 18 |
>> svn |
| 19 |
>> backend. I'm looking at this from a workflow perspective, in terms |
| 20 |
>> especially of the security issue around giving commit access to the whole |
| 21 |
>> tree. If the individual maintainer only has permission for those ebuilds |
| 22 |
>> s/he is responsible for, it might make it easier to allow new people |
| 23 |
>> write access. |
| 24 |
> |
| 25 |
> I fail to see any benefit from a layer above svn. svn has good access |
| 26 |
> control if we want use that built in. |
| 27 |
> |
| 28 |
So? Fair enough then. |
| 29 |
|
| 30 |
>> Sorry if this has all been discussed before. |
| 31 |
>> |
| 32 |
> Most likely the access control has been discusses some times before. To |
| 33 |
> summarize having access to everything is quite useful. |
| 34 |
> |
| 35 |
I can understand that; I'm not convinced that giving every dev access to the |
| 36 |
whole thing is necessary or desirable, but it may well be how gentoo likes |
| 37 |
to operate, and i have no quarrel with that. |
| 38 |
>> |
| 39 |
>> (Please note: I'm not discussing the mechanisms by which software might |
| 40 |
>> be installed for the end-user, rather the back-end which you devs use, of |
| 41 |
>> which I admittedly have no experience.) |
| 42 |
>> |
| 43 |
> So please let people who actually use/know how source control work |
| 44 |
> discuss the issue. |
| 45 |
|
| 46 |
Um, I do understand source control and have used it for other stuff. It just |
| 47 |
doesn't seem an ideal fit for this purpose. This really was motivated by a |
| 48 |
desire to lessen the workload for existing devs, but clearly it doesn't fit |
| 49 |
with the way gentoo works. No probs. |
| 50 |
|
| 51 |
|
| 52 |
-- |
| 53 |
gentoo-dev@g.o mailing list |
Archives