Hi,
Since this is a different question which got buried in the other
discussion, I appreciate it should be a new thread:
I'm a bit confused about all the portage tree stuff. There's just under
25,000 ebuilds, which are maintained by about 100 devs (not sure of exact
number, taken from a forum post.) I guess what I'm asking is why this isn't
just a database.
Please note, I'm not talking about applications like portage or pkgcore,
just the ebuild text files, which I understand have one maintainer?
I appreciate that source control is needed to maintain files over a period
of time and to roll back changes. Does that happen with ebuilds?
I'm thinking in any case that a db app can save old revisions or use a svn
backend. I'm looking at this from a workflow perspective, in terms
especially of the security issue around giving commit access to the whole
tree. If the individual maintainer only has permission for those ebuilds
s/he is responsible for, it might make it easier to allow new people write
access.
Sorry if this has all been discussed before.
(Please note: I'm not discussing the mechanisms by which software might be
installed for the end-user, rather the back-end which you devs use, of
which I admittedly have no experience.)
--
gentoo-dev@gentoo.org mailing list
Since this is a different question which got buried in the other
discussion, I appreciate it should be a new thread:
I'm a bit confused about all the portage tree stuff. There's just under
25,000 ebuilds, which are maintained by about 100 devs (not sure of exact
number, taken from a forum post.) I guess what I'm asking is why this isn't
just a database.
Please note, I'm not talking about applications like portage or pkgcore,
just the ebuild text files, which I understand have one maintainer?
I appreciate that source control is needed to maintain files over a period
of time and to roll back changes. Does that happen with ebuilds?
I'm thinking in any case that a db app can save old revisions or use a svn
backend. I'm looking at this from a workflow perspective, in terms
especially of the security issue around giving commit access to the whole
tree. If the individual maintainer only has permission for those ebuilds
s/he is responsible for, it might make it easier to allow new people write
access.
Sorry if this has all been discussed before.
(Please note: I'm not discussing the mechanisms by which software might be
installed for the end-user, rather the back-end which you devs use, of
which I admittedly have no experience.)
--
gentoo-dev@gentoo.org mailing list