Skip to contentSkip to conversation

SRCINSTALLDIR

DISCUSSION Russell Coker 2 participants 2 messages Aug 24, 2002 – Aug 26, 2002 SELinux security module

lore
Share & tools
lore
#0 lore raw

The operation of policy/Makefile in the new release does not include the policy version number in the source, and thus is based on the assumption that a policy.conf file will support multiple versions of the policydb.

This assumption does not hold for past versions, is there any reason that we can be sure it will hold for future versions? If not then I suggest that the right thing to do is to have a version number in the policy.conf file name (maybe policy.conf.11 or whatever the version is)?

Or do we consider it OK to have a source directory that doesn't contain the sources to all the binaries in the binary directory?

Signature · 3 lines
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
Quoted 1 line

From field.

--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#1 lore raw
Quoted 11 lines · Russell Coker

The operation of policy/Makefile in the new release does not include the policy version number in the source, and thus is based on the assumption that a policy.conf file will support multiple versions of the policydb.

This assumption does not hold for past versions, is there any reason that we can be sure it will hold for future versions? If not then I suggest that the right thing to do is to have a version number in the policy.conf file name (maybe policy.conf.11 or whatever the version is)?

Or do we consider it OK to have a source directory that doesn't contain the sources to all the binaries in the binary directory?

If we apply a version number to the source file, we should probably use a separate and independent version number that tracks changes to the policy language. The binary policy version number tracks changes to the binary policy format, so it may change without affecting the source file.

--
Stephen D. Smalley, NAI Labs
[email protected]

--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.