From kde-core-devel  Fri Sep 02 00:45:50 2005
From: Michael Pyne <pynm0001 () comcast ! net>
Date: Fri, 02 Sep 2005 00:45:50 +0000
To: kde-core-devel
Subject: Recent KACL merge in KIO 3.5
Message-Id: <200509012045.51048.pynm0001 () comcast ! net>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=112562177332330
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1552154.qUKrFyq7Eu"

--nextPart1552154.qUKrFyq7Eu
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I noticed that ACL support was recently added to KIO.  Unfortunately, it=20
breaks building kdelibs on my system.  I was simply going to fix it but I=20
need help with some things. ;)

Since it's part of kdelibs, I assume that KACL must always be available to =
be=20
linked against, even if the system doesn't support POSIX ACLs.  So this wou=
ld=20
mean that kacl.{h,cpp} must be included with appropriate #ifdefs to handle=
=20
HAVE_ACL, no?

If this isn't the case (and ACLs are only publicly exported through KFileIt=
em)=20
then I can simply #ifdef the appropriate definitions in kfileitem.cpp to fi=
x=20
the build I think.  But I doubt that's the case, and I don't know how to=20
implement KACL appropriately when ACL support is missing.

I have committed a fix for the Makefile.am though, so it's a start.

Regards,
 - Michael Pyne

--nextPart1552154.qUKrFyq7Eu
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBDF6C/qjQYp5Omm0oRAl3eAKC8z+mvlSmlUNVRDBsqDGYP5QEmcwCeLeHG
WwI0tvL+HfPGgeuQ6S2EV5I=
=t2Cg
-----END PGP SIGNATURE-----

--nextPart1552154.qUKrFyq7Eu--