| 1 |
On 23:51 Thu 06 Nov , Ryan Hill wrote: |
| 2 |
> On Thu, 6 Nov 2008 17:42:14 -0800 |
| 3 |
> Donnie Berkholz <dberkholz@g.o> wrote: |
| 4 |
> |
| 5 |
> > Once it hits the stable tree, only arch maintainers touch it from that |
| 6 |
> > point on. Package maintainers only work in the ~arch tree. |
| 7 |
> |
| 8 |
> What's the motivation behind this? I can think of several reasons why |
| 9 |
> a package maintainer would need to touch a stable ebuild. |
| 10 |
|
| 11 |
Could you provide a few examples? It's impossible for anyone else to |
| 12 |
come up with solutions to problems that haven't been described. |
| 13 |
|
| 14 |
Once it's stable, it should be static. If they need to make changes, |
| 15 |
they should make them in a new revision & stabilize it. That may require |
| 16 |
a slight change in our workflow to reduce stabilization periods in these |
| 17 |
cases. But I think it's a superior approach to an ever-changing single |
| 18 |
revision, as long as portage handles revisions of filenames instead of |
| 19 |
revisions of git. |
| 20 |
|
| 21 |
-- |
| 22 |
Thanks, |
| 23 |
Donnie |
| 24 |
|
| 25 |
Donnie Berkholz |
| 26 |
Developer, Gentoo Linux |
| 27 |
Blog: http://dberkholz.wordpress.com |
Archives