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.
<br><br>
<div><span class="gmail_quote">On 10/12/06, <b class="gmail_sendername">Nicholai Grønvald Hsu</b> &lt;<a href="mailto:ngh@er.dtu.dk">ngh@er.dtu.dk</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On 04:13 Mon 09 Oct&nbsp;&nbsp;&nbsp;&nbsp; , <a href="mailto:moritz.lutz@gmail.com">moritz.lutz@gmail.com</a> wrote:<br>&gt; Hi everyone,
<br>&gt; i think we should make a clear plan about who is porting what for arch64 in community.<br>&gt; Because at the moment there is a little bit confusen around.<br><br>I agree. It would be nice to concentrate the effort in a single
<br>(community?) repository. Should we setup some trusted users, like Arch<br>Linux, or is the Arch64 community so small we should all be able to<br>upload packages?<br><br>&gt; For my part i know i should look after x11 and xfce but i think i can do more but don't know
<br>&gt; if some one other is working on it allready.<br>&gt; So i think we should make a clear plan for it.<br><br>I wouldn't mind helping out with packages either, if needed.<br><br>/Nicholai<br><br>--<br>Civilingeniørstuderende
<br>Nicholai Grønvald Hsu<br>Danmarks Tekniske Universitet, IPL<br><br><br>_______________________________________________<br>arch-ports mailing list<br><a href="mailto:arch-ports@archlinux.org">arch-ports@archlinux.org</a>
<br><a href="http://www.archlinux.org/mailman/listinfo/arch-ports">http://www.archlinux.org/mailman/listinfo/arch-ports</a><br></blockquote></div><br>