[arch-general] Splitting up the 'boinc' package

[Karol Babioch]

Hi,

thank you very much for your reply.

On Fr, 2009-10-23 at 19:16 +0200, Jaroslav Lichtblau wrote:
> To be honest, I don't like the Debian structure of the boinc packages. 
> Arch also does not have any openssh-server/openssh-client packages.
> In my opinion AUR and ABS are the best places for providing such
> specialities.
For me it is just important that I can use boinc on my remote server
without X server installed. I could play around with aur/abs, but I
guess I'm not the only one who has installed Arch on a remote server, am
I?

Is there any policy forbidding both, the (classical) "boinc" package as
well as some of the "new" ones "boinc-client", "boinc-manager" and
"boinc-server"?

So anyone who just wants to run boinc could install the classical one,
and everyone else can precisely choose what components should be
installed?

I have noticed the exact same problems compiling the latest stable
release :(. But, as already said, according to the official site 6.6.41
is the latest release right now, so if you were able to compile 6.6.40
you may also be able to compile 6.6.41, which would it make easy to
split it up right then.

Could you share your PKGBUILD for 6.6.40? I've tried the one from the
repository, but it hadn't worked for me? May it have something to do
with some compiling flags? Although I reset my compiling flags to the
default, it hasn't worked, so whats wrong here?

Best regards
johnpatcher


-- 
Best regards,
Karol Babioch <karol at babioch.de>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://mailman.archlinux.org/pipermail/arch-general/attachments/20091024/a9a27d79/attachment.bin>