Firstly, apologies to all for my absence over the last week and a bit... Been away at my uncle's farm in outback Australia helping with mustering and branding cattle ;)
> I have one (probably stupid) question. How do we plan to build the packages > used for the initial phase? All of them are build on two different machines > (e.g. x64 and i686)? Or do we have a kind of build-farm? At the moment, I'm just building using 32 and 64 bit boxes I have available to me (work desktop and home desktop). I'm not sure what everyone else has available to them for this...? I was thinking about it while I was away and as far as installation goes, I think we will have to remaster the Arch install ISO's since our repos have different names (base, lamp and webapps vs core, extra and community). Either that or rename our repos to be the same as Arch, although that could be confusing and cause problems without a clear distinction between what is Arch Linux and what is ArchServer when dealing with repos. > Furthermore, what I am missing on the packages list is some kind of Ruby and > Java support. I do prefer Java and a lot of my own packages are Java > Packages. How are we going to handle these? I guess someone will need to maintain ruby / java packages... What needs Java on a server though...? > A further question is, if we are allowing the user to access the AUR of the > "normal" Arch Distribution? Arch Linux and AUR packages should be 100% compatible, but unsupported, on Arch Server since we're not changing the system much, just providing a stable set of packages mainly.
