[arch-ports] developing the (arch64) port

[Jason Chu]

On Tue, 04 Apr 2006 22:21:40 +0200
Andreas Radke <a.radke at arcor.de> wrote:

> After some discussions between the x86_64 devs we agree that a common
> pkgbuild tree is a good solution. It will bind us to follow arch32 as
> much as possible but that's what a port only is. And that's ok.
> 
> It would be to dangerous to have a separate tree so it would be a fork
> from the beginning on. That's not what we want to become.
> 
> In our view we cannot see anything what holds us from joining your
> party.
> 
> In my view we don't really need certain cvs trunks. I guess the i686
> devs don't have the intention to move to svn so we will have to work
> with the same cvs they already use. For checkout we can use csup and
> for committing cvs. I suggest to keep using first pkgrel number for
> the i686 packages as you do now. So i686 would build every new pkg
> with a pkgrel nr. -1. When you fix something you go with -2. Nothing
> new.
> 
> Even if nothing will make now use of it I suggest to add an "arch" tag
> to every pkg for each architecture. Just like Gentoo and Frugal do. So
> every i686 release will get // arch='i686' // tag.
> 
> Every package the x86_64 devs will have to port. If it is ok
> everything stays like it is and we add // arch='i686' 'x86_64' //
> tag. If a 64bit bugfix is needed we will do a pkg foo-1.1 so only the
> x86_64 binary will be built. i686 fixes we could leave out if we are
> not affected but in almost every case we follow and do our own foo-2
> pkg.
> 
> Once we have a pkg marked with our arch x86_64 tag we can think about
> to try to automatically build next release. But before moving to
> current each time a 64bit dev will have to mark it for really working
> well.
> 
> Is that a way we can go?
> 
> So I don't see why we should wait any longer.
> 
> Things like crossbuilding with pacbuild and AUR we can add later.
> 
> AndyRTR

Alright, because you're such a nice guy, here's what I'm prepared to do
for you.

We'll set you guys up with pserver access to our cvs server (just like
the TUs have).

Then we'll set up a set of repo update daemons (just like the TUs have).

Then you guys can make your PKGBUILD updates, tag your builds (right
now we use CURRENT, you guys can use CURRENT-x86_64), and upload the
built packages.

A script will process the PKGBUILD updates and recreate the repos when
it needs to.

That's about it.

Now, here's the catch.  It's gonna take me/us a while to set it up.
Work is crazy busy for me and there are only a few people who have
experience using the TU daemons and they will need to be modified to
work for your purposes.

I'm going to set the clock at 2 weeks from today.  By the 18th of
April. we will have something for you guys to start contributing
through.

Jason
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://archlinux.org/pipermail/arch-ports/attachments/20060404/b2d1b7ce/attachment.pgp>