On Sun, 2014-11-30 at 21:52 +0000, Schaufler, Casey wrote: > > -----Original Message----- > > From: Dev [mailto:[email protected]] On Behalf Of Patrick Ohly > > Sent: Friday, November 28, 2014 1:53 AM > > To: Tizen Dev > > Subject: [Dev] default Smack manifests > > > > Hello! > > > > Kevin recently noticed and/or was told that it is no longer necessary to > > have %manifest entries in the %files sections of a .spec file if the > > default manifest is sufficient: > > > > <manifest> > > <request> > > <domain name="_"/> > > </request> > > </manifest> > > > > Apparently builds in OBS add such a manifest automatically; experiments > > confirm that. But can someone please also confirm that officially? > > The official word is that every package needs a manifest. > > > According to the Wiki, one has to add it explicitly: > > > > https://wiki.tizen.org/wiki/Security:SmackThreeDomainModel > > "Each Tizen package needs a manifest file." > > > > If %manifest has become optional, then gbs needs to be fixed such that > > it behaves like OBS: when compiling SyncEvolution with gbs 0.22.3, > > files in e.g. /usr/bin from the resulting .rpm have the "User" label. > > When installing the .rpm from OBS, they have "_" (as it should be). > > That's one of the reasons that we're still requiring the manifest file.
In the meantime, Casey told me that the approach of using the manifests to set Smack labels was abandoned in Tizen 3. Let me relay that information here so that everyone is on the same page. I fully support that direction. It's clear that manifest support in current Tizen 3.0 is barely needed at all anymore (but see below), and getting rpm to work with the Tizen patches in "Tizen on Yocto" was/is a major headache. But what does that mean for packages in Tizen 3.0? Will those packages which depend on a non-standard manifest (like filesystem [1]) be changed, and when? [1] https://review.tizen.org/git/?p=platform/upstream/filesystem.git;a=blob;f=packaging/filesystem.manifest;h=3cfcd1e775ff7415ead295df4cb856ec0c31403c;hb=refs/heads/tizen -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
