| 1 |
lurker wrote: |
| 2 |
> On 28/07/08 18:18, Chris Gianelloni wrote: |
| 3 |
>> Just a little FYI for everybody on the list... |
| 4 |
>> |
| 5 |
>> I've gone and forked most of the Release Engineering tools. I no longer |
| 6 |
>> plan on maintaining the "Gentoo" versions of catalyst, genkernel, |
| 7 |
>> hwdata, or livecd-tools. Instead, I am working on these projects under |
| 8 |
>> my own domain and will be releasing them as "standalone" applications, |
| 9 |
>> not under the Gentoo moniker. Now, these projects always have been |
| 10 |
>> "Gentoo Hosted Projects" and not really owned by the Gentoo project, but |
| 11 |
>> continued issues from other developers has proven that many don't |
| 12 |
>> understand this case. As such, it was simply easier to break away from |
| 13 |
>> the main project. This also allows us greater flexibility in making |
| 14 |
>> changes that would otherwise not be accepted within Gentoo. All of the |
| 15 |
>> current maintainers of these forks will be working on them in their new |
| 16 |
>> homes, making the Gentoo-hosted versions essentially dead. |
| 17 |
> |
| 18 |
> Interesting development. Can we be confident that the new independent |
| 19 |
> catalyst will not break the current interfaces (ignoring trivial |
| 20 |
> changes) and the use of portage? More to the point: what does this mean |
| 21 |
> for existing catalyst projects that are using portage and intend to stay |
| 22 |
> with it? |
| 23 |
|
| 24 |
No, you cannot be confident of that. You never have been able to. We tend to |
| 25 |
"break" things all the time. However, we do our best not to :) |
| 26 |
|
| 27 |
Catalyst will always be compatible with portage (at least, we won't |
| 28 |
intentionally break it). We'll also be adding support for pkgcore and perhaps |
| 29 |
focusing more on that particular PM in the future. |
| 30 |
|
| 31 |
-- |
| 32 |
Andrew Gaffney http://dev.gentoo.org/~agaffney/ |
| 33 |
Gentoo Linux Developer Catalyst/Installer + x86 release coordinator |
Archives