Since Arch64 is an offical port, I think it should work the same as regular Arch Linux. TUs should be established and thus the repo would be well managed. Also, considering that most PKGBUILDs work on both platforms with only slight changes, it would be easy to get things going. On 10/12/06, Nicholai Grønvald Hsu wrote:

On 04:13 Mon 09 Oct , moritz.lutz@gmail.com wrote:

...

Hi everyone, i think we should make a clear plan about who is porting what for arch64 in community. Because at the moment there is a little bit confusen around.

I agree. It would be nice to concentrate the effort in a single (community?) repository. Should we setup some trusted users, like Arch Linux, or is the Arch64 community so small we should all be able to upload packages?

...

For my part i know i should look after x11 and xfce but i think i can do more but don't know if some one other is working on it allready. So i think we should make a clear plan for it.

I wouldn't mind helping out with packages either, if needed.

/Nicholai

-- Civilingeniørstuderende Nicholai Grønvald Hsu Danmarks Tekniske Universitet, IPL

_______________________________________________ arch-ports mailing list arch-ports@archlinux.org http://www.archlinux.org/mailman/listinfo/arch-ports

On Fri, 13 Oct 2006, Pierre Schmitz wrote:

Am Montag, 9. Oktober 2006 04:13 schrieb moritz.lutz@gmail.com:

...

Hi everyone, i think we should make a clear plan about who is porting what for arch64 in community. Because at the moment there is a little bit confusen around. For my part i know i should look after x11 and xfce but i think i can do more but don't know if some one other is working on it allready. So i think we should make a clear plan for it.

As a TU wouldn`t it be possible to maintain i686 and x86_64-packages at the same time oder will there be two seperate "communities"?

There was a discussion about that on the TUR ML: http://www.archlinux.org/pipermail/tur-users/2006-August/003172.html IIRC, the consensus was to only have one TU group that will maintain both the i686 and x86_64 community repo. The present problem is that very few current TU have a 64 bits machine to port/maintain the x86_64 repo. The TU group could certainly need new TUs that would focus on porting/maintaining 64 bits version of the community repo packages. If you are interested in becoming a TU to work on the x86_64 community repo (and/or the i686 repo), please present yourself on the TUR ML. Eric a.k.a Snowman (TU) -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.