local_mainfest.xml

local_mainfest.xml

[William Roberts]

[-- Attachment #1: Type: text/plain, Size: 128 bytes --]

Is the local_manifest file under git revision control somewhere that we
could track from?

-- 
Respectfully,

William C Roberts

[-- Attachment #2: Type: text/html, Size: 183 bytes --]

Re: local_mainfest.xml

[Stephen Smalley]

On Mon, 2012-05-21 at 10:22 -0700, William Roberts wrote:
> Is the local_manifest file under git revision control somewhere that
> we could track from?

Not presently.  If it would be helpful, we could set one up, but we
should make sure we work out how it should be organized up front.  At
present, we provide 6 versions of the local_manifest.xml file.  There
are three baselines (master, 4.0.3, 4.0.4) and two fetch URLs (one
git-based and one http-based).  The repo could contain two files
(local_manifest.xml and local_manifest_http.xml) with three branches
(master, seandroid-4.0.3, seandroid-4.0.4), thereby mirroring the
structure of the other git projects.  Is that what you would want?  Did
you need/want any of the older versions of the files included in the
history (if so, which ones?) or just start from the current ones?

-- 
Stephen Smalley
National Security Agency


--
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.

RE: local_mainfest.xml

[Radzykewycz, T (Radzy)]

Sounds like a good organization to me.

You might want to name the branches similar to what AOSP uses, but mayme with "se" or "se_" prepended.  E.g. se_android-4.0.3_r1 instead of seandroid-4.0.3

In the past, there were times I would have liked the history, but I don't need it now.

________________________________________
From: owner-selinux@tycho.nsa.gov [owner-selinux@tycho.nsa.gov] on behalf of Stephen Smalley [sds@tycho.nsa.gov]
Sent: Monday, May 21, 2012 10:53 AM
To: William Roberts
Cc: selinux@tycho.nsa.gov; seandroid@tycho.nsa.gov
Subject: Re: local_mainfest.xml

On Mon, 2012-05-21 at 10:22 -0700, William Roberts wrote:
> Is the local_manifest file under git revision control somewhere that
> we could track from?

Not presently.  If it would be helpful, we could set one up, but we
should make sure we work out how it should be organized up front.  At
present, we provide 6 versions of the local_manifest.xml file.  There
are three baselines (master, 4.0.3, 4.0.4) and two fetch URLs (one
git-based and one http-based).  The repo could contain two files
(local_manifest.xml and local_manifest_http.xml) with three branches
(master, seandroid-4.0.3, seandroid-4.0.4), thereby mirroring the
structure of the other git projects.  Is that what you would want?  Did
you need/want any of the older versions of the files included in the
history (if so, which ones?) or just start from the current ones?

--
Stephen Smalley
National Security Agency


--
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.


--
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.

RE: local_mainfest.xml

[Stephen Smalley]

On Mon, 2012-05-21 at 18:17 +0000, Radzykewycz, T (Radzy) wrote:
> Sounds like a good organization to me.
> 
> You might want to name the branches similar to what AOSP uses, but mayme with "se" or "se_" prepended.  E.g. se_android-4.0.3_r1 instead of seandroid-4.0.3
> 
> In the past, there were times I would have liked the history, but I don't need it now.

Just to clarify: The reason for using e.g. seandroid-4.0.3 rather than
seandroid-4.0.3_r1 in our other projects is that seandroid-4.0.3 is a
branch rather than a tag.  Thus, we can keep back-porting changes from
our master branch as well as merging subsequent releases of 4.0.3 (e.g.
going to android-4.0.3_r1.1).  The local_manifest.xml file then just
refers to seandroid-4.0.3 and doesn't need to be changed each time.

So I think we'll just use consistent names with our existing branches in
other projects; the local_manifest.xml file on the seandroid-4.0.3
branch will refer to the seandroid-4.0.3 branches of the other projects.

-- 
Stephen Smalley
National Security Agency


--
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.

RE: local_mainfest.xml

[Stephen Smalley]

On Mon, 2012-05-21 at 16:32 -0400, Stephen Smalley wrote:
> On Mon, 2012-05-21 at 18:17 +0000, Radzykewycz, T (Radzy) wrote:
> > Sounds like a good organization to me.
> > 
> > You might want to name the branches similar to what AOSP uses, but mayme with "se" or "se_" prepended.  E.g. se_android-4.0.3_r1 instead of seandroid-4.0.3
> > 
> > In the past, there were times I would have liked the history, but I don't need it now.
> 
> Just to clarify: The reason for using e.g. seandroid-4.0.3 rather than
> seandroid-4.0.3_r1 in our other projects is that seandroid-4.0.3 is a
> branch rather than a tag.  Thus, we can keep back-porting changes from
> our master branch as well as merging subsequent releases of 4.0.3 (e.g.
> going to android-4.0.3_r1.1).  The local_manifest.xml file then just
> refers to seandroid-4.0.3 and doesn't need to be changed each time.
> 
> So I think we'll just use consistent names with our existing branches in
> other projects; the local_manifest.xml file on the seandroid-4.0.3
> branch will refer to the seandroid-4.0.3 branches of the other projects.

This repository has been created; you can clone it via:
git clone git://git.selinuxproject.org/~seandroid/manifests

There are three branches available: master, seandroid-4.0.3, and
seandroid-4.0.4.

-- 
Stephen Smalley
National Security Agency


--
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.

Re: local_mainfest.xml

[William Roberts]

[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]

I think that would be ok; I like the 2 files, 3 branches approach with the
names similar to aosp's branch names.

Currently I maintain my own manifest repository that includes some of your
stuff, and I want to keep the manifests up to date and having them in git
would make it much easier. Currently their a logical merge of
local_manifest.xml and default.xml. You could just start with the present
files, I don't need history from before present.

Bill

On Mon, May 21, 2012 at 10:53 AM, Stephen Smalley <sds@tycho.nsa.gov> wrote:

> On Mon, 2012-05-21 at 10:22 -0700, William Roberts wrote:
> > Is the local_manifest file under git revision control somewhere that
> > we could track from?
>
> Not presently.  If it would be helpful, we could set one up, but we
> should make sure we work out how it should be organized up front.  At
> present, we provide 6 versions of the local_manifest.xml file.  There
> are three baselines (master, 4.0.3, 4.0.4) and two fetch URLs (one
> git-based and one http-based).  The repo could contain two files
> (local_manifest.xml and local_manifest_http.xml) with three branches
> (master, seandroid-4.0.3, seandroid-4.0.4), thereby mirroring the
> structure of the other git projects.  Is that what you would want?  Did
> you need/want any of the older versions of the files included in the
> history (if so, which ones?) or just start from the current ones?
>
> --
> Stephen Smalley
> National Security Agency
>
>


-- 
Respectfully,

William C Roberts

[-- Attachment #2: Type: text/html, Size: 1996 bytes --]