On Sun, Jun 08, 2003 at 12:49:30PM +0200, Marcel Pol wrote:
I also have an oldworld PowerMac 185 Mhz, 96 Mb ram.
It's mostly too slow to compile anything, but it does run cooker.
I believe Ben Reser has a few ppc machines, but I don't know if he runs cooker
on it.
I've tried to run cooker on
On Sun Jun 08, 2003 at 09:49:20AM +0200, Stefan van der Eijk wrote:
Also, don't forget updates. Unless the people who build these ports are
willing to maintain a system/chroot/whatever dedicated for 18mos for
building updates for these ports, it won't happen. As Stefan says, making
this stuff
But, we might be getting to the point where we actually need a cooker
extranet. For example, I would like to be able to remove build output on
an automated build host to get a package rebuilt, but we wouldn't want
anyone to be able to remove build output ...
It seems installer need works
IMHO
Releasing means supporting. supporting a product requires an
organisation and knowledge being available. It also needs to be
worthwhile -- bring some $$$ to the company. For the alpha, mips,
pa-risc and sparc the market is too small.
Since I'm more or less the maintainer of the alpha
On Sun, 08 Jun 2003 09:36:05 +0200
Stefan van der Eijk [EMAIL PROTECTED] wrote:
At the moment, to my knowledge we have the following machines _dedicated_
to non-intel cooker development (please, developers, fill in all blanks):
Alpha
- 2 x XP1000 - CSC still 7.1b - need help with this
- 1
Hello,
Thanks for the feedback on the idea. Now, I would like to summarise some
points that aroused in your replies.
1) MandrakeSoft might be reluctant to take the non-Intel ports under it's
wings. This of course makes sense (as Stefan noticed, support = money, and
we cannot ask the company
2) We (the community) have resources to keep the cooker tree up to
date, with exception of Drak* tools.
Not all, only the ones who deals with the hardware.
However with more machines to rebuild packages (and with centralised
and automated extranet) we may be able to make it for the next
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 08 June 2003 15:59, Michael Scherer wrote:
and, when you say a extranet, do you mean some kind of vpn, with access
for the community ? if so, then using a crosscompiler and , maybe
distcc will allow to have more ressources avaliaible, but
On nie 8. czerwca 2003 14:59, Michael Scherer wrote:
However with more machines to rebuild packages (and with centralised
and automated extranet) we may be able to make it for the next
release.
what about using a cross compiler ? If done properly, people just have
to install a rpm on a
Yes, by extranet, I meant VPN. And as you can see, we already have
distcc working on the sparcs. (Thanks Per Oyvind! :)
Mhh, do you think that distcc could work on a vpn ? isn't there some
issues about the bandwidth ?
BTW, What are our options for building the VPN? IP-IP, IP-GRE (easy
to
On Fri, 6 Jun 2003, Jaroslaw Zachwieja wrote:
At the moment, to my knowledge we have the following machines _dedicated_
to non-intel cooker development (please, developers, fill in all blanks):
PPC
- 1 x ?? - Olivier Thauvin
- others?
I've let Olivier take over cooker PPC
Jaroslaw Zachwieja wrote:
But, we might be getting to the point where we actually need a cooker
extranet. For example, I would like to be able to remove build output on
an automated build host to get a package rebuilt, but we wouldn't want
anyone to be able to remove build output ...
Well,
Le Samedi 07 Juin 2003 20:55, Stefan van der Eijk a écrit :
Jaroslaw Zachwieja wrote:
But, we might be getting to the point where we actually need a cooker
extranet. For example, I would like to be able to remove build output on
an automated build host to get a package rebuilt, but we
On Sat Jun 07, 2003 at 08:55:46PM +0200, Stefan van der Eijk wrote:
IMHO
Releasing means supporting. supporting a product requires an
organisation and knowledge being available. It also needs to be
worthwhile -- bring some $$$ to the company. For the alpha, mips,
pa-risc and sparc the
Well, SPARC's (and at some point Alpha and Opteron 240 SMP) at CSC are
on private network behind 9.1 i586 box. I can't see anything that
should stop us from creating the extranet and have the builds automated
and
coordinated. Some centralised user authentication might be a good idea
at
15 matches
Mail list logo
