Messages in this thread | | | Date | Fri, 2 May 2008 15:30:05 +0200 (CEST) | From | Jan Engelhardt <> | Subject | Re: Btrfs v0.14 Released |
| |
On Friday 2008-05-02 14:52, Chris Mason wrote: >> >> An alternative approach, and IMHO better suited, is to: >> >> make -C ${kdir} all I_HAZ_AN_APPARMOR=1 > >This is better than the current situation (oops without any clues), but I'd >prefer that people not have to know what apparmor is or if they have it.
I guess iff people have a clue just what btrfs is and what it is good for and why one would need it, I guess they also know of Apparmor. If not, well, I hope you mentioned it in the INSTALL file! Documentation on the most important things is always a good thing.
>(This isn't a knock on apparmor, I'd just rather take care of it >automagically).
Well you could go down the conftest.sh route, but I dislike that approach because such a Makefile system tries to be smarter than me; and that often breaks because developers made a mess out of the remaining Makefile and before long, it broke on odd, but "standards-conforming", O= builds. (Fun stories with nvidia.)
| |