| 1 |
On 28/07/08 18:18, Chris Gianelloni wrote: |
| 2 |
> Just a little FYI for everybody on the list... |
| 3 |
> |
| 4 |
> I've gone and forked most of the Release Engineering tools. I no longer |
| 5 |
> plan on maintaining the "Gentoo" versions of catalyst, genkernel, |
| 6 |
> hwdata, or livecd-tools. Instead, I am working on these projects under |
| 7 |
> my own domain and will be releasing them as "standalone" applications, |
| 8 |
> not under the Gentoo moniker. Now, these projects always have been |
| 9 |
> "Gentoo Hosted Projects" and not really owned by the Gentoo project, but |
| 10 |
> continued issues from other developers has proven that many don't |
| 11 |
> understand this case. As such, it was simply easier to break away from |
| 12 |
> the main project. This also allows us greater flexibility in making |
| 13 |
> changes that would otherwise not be accepted within Gentoo. All of the |
| 14 |
> current maintainers of these forks will be working on them in their new |
| 15 |
> homes, making the Gentoo-hosted versions essentially dead. |
| 16 |
|
| 17 |
Interesting development. Can we be confident that the new independent |
| 18 |
catalyst will not break the current interfaces (ignoring trivial |
| 19 |
changes) and the use of portage? More to the point: what does this mean |
| 20 |
for existing catalyst projects that are using portage and intend to stay |
| 21 |
with it? |
Archives