[OGo-Users] rpm's for opensuse 10.3

[Adam Tauno Williams]

--=-95PqhnyIO9fJLwzKmMuK
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

> > The filename still says openSUSE 10.2,  but only because I can't figure
> > out how to change that in without deleting and recreating, and thus
> > relinking, in the plone.  Description says 10.3 =20
> Do you have the rpm's for x86_64 too?

Nope.  Just never had the need;  OGo scales much better via multiple
heads (el'cheapo 32-bit pizza boxes) than from gargantuan address space.
PostgreSQL on the other hand loves 64-bit.

> If not could you please upload the src.rpm that you used?
> Or can I take the same that is there for 10.2, would that work for 10.3 t=
oo?

There really isn't any difference,  just what they get linked to at
compile time.  IMy SPEC files are in the PLONE.  Then just put
ogo-gnustep_make.tar.gz,  sope.tar.gz, and opengroupware.tar.gz
in /usr/src/packages/SOURCES/  Then it should just "rpmbuild -bb {spec
file}".

http://docs.opengroupware.org/Members/whitemice/misc/OGoSUSESPECFiles.tar.g=
z/file_view

You of course have to tweak the version numbers appropriately in the
header of the SPEC files.

> > These packages reflect r1551/r2051 + task::qsearch command,
> > ogo-qsearch-task tool, and the OGoTaskAccessHandler object.  The later
> > *might* cause you issues,  it isn't completely tested yet [and I think
> > something is wrong,  but actually in detecting project access].
> I hope I get my desktop updated next week to 10.3, then I can test these =
on=20
> it.


--=-95PqhnyIO9fJLwzKmMuK
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQBHStcYLRePpNle04MRAoNYAJ4nvpielakf7uKWO5w7txyrlBWB5gCfbIFn
iV4NH9HlJUlOQW70N/IaXxk=
=vCXW
-----END PGP SIGNATURE-----

--=-95PqhnyIO9fJLwzKmMuK--