On Mon, 2009-05-25 at 15:31 +0200, Kern Sibbald wrote: > > > > Uh I would say we could it a bit different, we check if --enable-acls is > > set (so thats different then now) and then complain if things are not > > installed. Then we can easily change the configure used in the rpm building > > (SPEC file) to include --enable-acl. We could do the same for xattr > > support. So we only act when someone explicitly enabled acl and xattr > > support. > > Yes, I think this would be a very reasonable solution. > Ok, that leaves thing still in automatic mode like it is now but will scream when you enable something and it doesn't make sense because you are missing the proper requirements.
> > > > As far as I know its now either enable it when found or disable it when > > --disable-acl is given. > > That is a very reasonable behavior, but in addition, if we *require* it if > the > user explicitly puts --enable-acls the ./configure should fail if the > libraries are not available -- I think that is what you suggested above. Correct, sometimes my English is kinda sloppy, I write tend to forget the not word in some sentences and then it reads somethings completely different. > > Is that something you would like to do, or should I do it? > I could have a look, but if you think you can do it soon I don't mind you doing it. I need to see how to tweak configure.in to do the "proper" thing. Marco ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
