-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Piotras.

- --On 05.06.2002 15:31:49 +0200 pp wrote:

>> > And of course how are we build packages for different php versions?
>> > I do not have so many machines here :)
>> 
>> Ok, I lost track now entierly... :-(
> 
> If You want to build debian unstable package, the best thing You may
> do  is have debian unstable system running and just upgraded.
> The same for testing and stable.

Ok. And the packages are built from us. It is _not_ so, that we only
upload source packages and some automatic build system builds the
packages for the different architectures. Right?


>> Just tell me what you need to build Debian Packages, and as soon as
>> 1.4.3 final is out, we can start right away.
> 
> As I wrote , optimal configure options for mod and lib.

For 1.4.3 they should already be done with my last checkin (which
didn't make it to midgard-cvs again). All packages (mod,lib,php4) will
now compile good with default options in a "default" environment,
including Debian. I've even optimized the php4-package to use defaults
in the macros, rather then in the mkall/rules-scripts. So you should go
fine with an ./configure --prefix=/usr for mod/lib and a
phpize/configure for php4.


>> We just have to build up our own archive as with the structure
>> proposed on -dev. We just have to decide, which binary packages we
>> will put into the CVS there. I opt for "testing-compatible" packages
>> as our stable and testing trees, and for "unstable-compatible"
>> packages for our own unstable tree.
> 
> deb http://www.midgard-project.org/developer/downloads/debian midgard
> sid
> 
> Official repository for unstable and testing packages which should
> have the same version , and should be builded almost at the same time
> , which will help migrate package from unstable to testing on
> official servers.
> This repository is also for DD who will upload packages to official
> distribution.
> 
> 
> deb http://www.midgard-project.org/developer/downloads/debian cvs sid
> 
> cvs packages , not official , for testing and development.
> 
> Did I missed something?

Basically not. Based on what I already wrote here is a refinement:

- --- I wrote on Midgard-Dev on 22 May 2002:

> unstable -> STABLE-VERSION-CVS-DATE Packages
>   This is where nightly Builds will go. Schema as it is now
> testing -> STABLE-VERSION-COUNT Packages
>   This is were i.e. Release Candidates will go. Schema will be like it
>   is a stable version, the current RC would be named 1.4.3-1.
>   Subsequent   releases will just increase the counter. It is
>   explicitly not named   RC, because prereleases will also go there.
> stable -> STABLE-VERSION[-COUNT] Packages
>   Only final releases will go here. would be 1.4.3 currently. Security
>   backports will be done with the counter increased.

Which would lead to this (All Archives will have the usual symlinks
stable,testing and unstable):

deb http://..../downloads/debian/ (potato|woody|sid) stable 

   => For official packages, which are the basis for the official Debian
      Archives. Package naming scheme: libmidgard_1.4.3-x.deb

deb http://..../downloads/debian/ (potato|woody|sid) testing

   => Our Release Candidates and Prereleases intended for testing. If
it 
      is possible to build this automagically, it would be really great.
      Package naming scheme: libmidgard-testing_1.4.3-x.deb

deb http://..../downloads/debian/ (potato|woody|sid) unstable

   => CVS Snapshots for use from developers only. Again, it would be
      great if this could be generated automatically...
      Package naming scheme: libmidgard-unstable-20020601.deb

I'd like to keep the naming scheme stable/testing/unstable for our
repository too to be able to offer a wide range of testing abilities.
Of course we have to watch out to make the different package types
(stable,testing and unstable) conflicting each other.

I can only provide a Debian woody machine for package building (Nathan
Syntronics).


Live long and prosper!
Torben Nehmer

- --
Torben Nehmer, Munich, Germany
http://www.nathan-syntronics.de, mailto:[EMAIL PROTECTED]
PGP Public Key ID on wwwkeys.(de.)pgp.net: 0x7E9DE456
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE8/iCcJPh4Kn6d5FYRAmpVAKD8ZjG9qFlMFDJhPyxQu7PdUmAycQCgqzof
iURhyqTEKn3SwEo/p+6Fptk=
=0/CI
-----END PGP SIGNATURE-----


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to