From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Joshua Brindle <method@gentoo.org>
Cc: selinux <selinux@tycho.nsa.gov>
Subject: Re: [RFC] Upstream policy handling
Date: Sun, 19 Sep 2004 20:21:08 +0100 [thread overview]
Message-ID: <20040919192108.GD23901@lkcl.net> (raw)
In-Reply-To: <414DA0A7.1000708@gentoo.org>
On Sun, Sep 19, 2004 at 11:07:19AM -0400, Joshua Brindle wrote:
> If there are any other suggestions or comments on this I'd like to hear
> them. Obviously the implementation details are up in the air here, and I
> know that some of you can't/won't use bk. If there are suggestions for a
> better system and a way to host it (preferably neutrally) that would
> be great.
a little understood and even less deployed method of using
cvs is to checkout a repository with a tag (e.g. NSA) and then
checkout individual files with a different tag (e.g. REDHAT).
the REDHAT repository should contain *only* the files that are
different (or extra).
first you do a cvs co -r NSA and then you do a cvs update -r REDHAT.
what happens is that the files in the REDHAT repository overwrite
those in the mainly NSA local checkout: examination of CVS/Entries
shows a mixed selection of NSA and REDHAT tags.
note that you _cannot_ due to a bug do a cvs co followed
by a cvs update -r REDHAT. if you then look in valtags
(in CVSROOT on in this case the sourceforge repository)
then you will find that there is an entry with two spaces:
this causes all subsequent cvs operations to fail until the
file is MANUALLY edited. yes a bug was raised about this,
and even a patch produced (several years ago) and no the cvs
maintainers haven't bothered to fix it.
a small script could be written to do the checkouts.
maintainers of the REDHAT repository simply add whatever files that
are different from the NSA repository to the REDHAT repository.
one other thing that's useful is of course cvs diff -r NSA to check
the differences between the REDHAT files and NSA ones: this works
as expected.
cvs update also works as expected.
the only thing is that from a maintenance point of view (commits)
it will be necessary to write some scripts (to go in CVSROOT)
that double-check who is allowed to commit to the NSA tag and
who to the REDHAT one.
at this point i'd recommend doing the same trick as above, with
subversion, over cvs any day...
l.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2004-09-19 19:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 15:07 [RFC] Upstream policy handling Joshua Brindle
2004-09-19 19:21 ` Luke Kenneth Casson Leighton [this message]
2004-09-19 21:10 ` Luke Kenneth Casson Leighton
2004-09-19 20:46 ` Russell Coker
2004-09-19 21:11 ` Joshua Brindle
2004-09-19 21:29 ` Russell Coker
2004-09-19 23:48 ` Joshua Brindle
2004-09-20 3:33 ` Colin Walters
2004-09-20 12:26 ` Daniel J Walsh
2004-09-20 12:56 ` Christopher J. PeBenito
2004-09-20 15:53 ` Colin Walters
2004-09-20 20:44 ` File types that are not sysadmfiles Daniel J Walsh
2004-09-21 5:08 ` Russell Coker
2004-09-21 14:42 ` Colin Walters
2004-09-21 15:25 ` Russell Coker
2004-09-21 15:45 ` Colin Walters
2004-09-21 14:42 ` Colin Walters
2004-09-22 20:22 ` James Carter
2004-09-23 16:43 ` [RFC] Upstream policy handling Daniel J Walsh
2004-09-23 19:10 ` Russell Coker
2004-09-20 12:25 ` Luke Kenneth Casson Leighton
2004-09-20 14:54 ` Russell Coker
2004-09-19 22:08 ` Colin Walters
2004-09-19 23:24 ` Joshua Brindle
2004-09-20 0:07 ` Colin Walters
2004-09-20 12:22 ` Luke Kenneth Casson Leighton
2004-09-20 15:17 ` Thomas Bleher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040919192108.GD23901@lkcl.net \
--to=lkcl@lkcl.net \
--cc=method@gentoo.org \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.