aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorYong-iL Joh <yong-il.joh@windriver.com>2016-08-24 10:05:38 +0900
committerYong-iL Joh <yong-il.joh@windriver.com>2016-08-24 14:21:02 +0900
commit8f0e1ff23c16bffeda19e3fa14f9217475add890 (patch)
treef09815a029d852a06e988d1086e7cdc8fe48b93f
parentadba681f8754712f09300e9df7664a6f61d78925 (diff)
downloadmeta-ivi-8f0e1ff23c16bffeda19e3fa14f9217475add890.tar.gz
meta-ivi-8f0e1ff23c16bffeda19e3fa14f9217475add890.tar.bz2
meta-ivi-8f0e1ff23c16bffeda19e3fa14f9217475add890.zip
README.md: updated
- updated meta-openembedded - split the comment about SRC_URI to README.SRC_URI Signed-off-by: Yong-iL Joh <yong-il.joh@windriver.com>
-rw-r--r--README.SRC_URI50
-rw-r--r--README.md46
2 files changed, 51 insertions, 45 deletions
diff --git a/README.SRC_URI b/README.SRC_URI
new file mode 100644
index 0000000..4f87a96
--- /dev/null
+++ b/README.SRC_URI
@@ -0,0 +1,50 @@
+talk about using SRCREV instead of branch or tag at SRC_URI
+-----------------------------------------------------------
+
+Sent: Tuesday, April 05, 2016 11:33 PM
+To: James Thomas
+Cc: genivi-meta-ivi@lists.genivi.org
+Subject: Re: [meta-ivi] Building with local source mirror
+
+On Tue, Mar 29, 2016 at 10:51 PM, James Thomas <james.thomas@codethink.co.uk> wrote:
+> One thing I noticed is that simply providing the SRCREV works as long
+> as that sha exists within master, if it doesn't then you have a build
+> error, so being able to use tags is useful.
+>
+> I think using git://...;tag=foo is not sufficient, because tags *can*
+> change (i.e there's no guarantee that the tag you're using is going to
+> be the same as the one you used yesterday).
+>
+> What would be nice is if you could go tag=foo, and have it verified
+> against SRCREV (in my testing this resulted in a build error *when*
+> the tag and sha matched)
+>
+> However, something like
+>
+> SRC_URI = "git://mygitrepo/foo.git;nobranch=1;branch=v0.2"
+> SRCREV = "7654321"
+>
+> does enforce that check (v0.2 is actually a tag in this case), which
+> seems to be pretty useful (the recipe provides something human
+> readable, and something a machine can understand, and will always
+> check they match)
+
+I completely understand the reasoning behind this. The point I'm trying to
+ make is that the automotive industry has a strong need for reproducible
+ offline builds and any kind of mandatory online checks break this requirement.
+ And like Federico said, using SRCREV is also the Yocto project practice.
+
+If we want meta-ivi to be widely used in the industry I believe it should
+ support it's needs. In my opinion the same should go for the whole GENIVI
+ stack to work nicely, which in particular means tags of the projects should
+ not change. But the easiest solution would be for meta-ivi to not use tags.
+ That way it supports offline builds and it is also possible to track bugfixes
+ in the projects instead of pinning to the tag and then getting the bugfixes
+ in patch by patch until next release.
+
+How do the others on this list feel about this proposal?
+
+Regards,
+--
+Igor Socec
+Software Engineer
diff --git a/README.md b/README.md
index 0405a01..4a9c260 100644
--- a/README.md
+++ b/README.md
@@ -30,7 +30,7 @@ Layer Dependencies
URI: git://git.yoctoproject.org/poky
> branch: krogoth
-> revision: f7b994b75261550faa3ccf9005fc174950c7bee9
+> revision: 12eb72ee3b02f826a156ff4e396c770f2b93571e
URI: git://git.openembedded.org/meta-openembedded
> layer: meta-oe
@@ -91,47 +91,3 @@ export TEMPLATECONF=/full/path/to/meta-ivi/meta-ivi/conf
5. To login use these credentials:
> User - root
> Password - root
-
-
-talk about using SRCREV instead of branch or tag at SRC_URI
------------------------------------------------------------
-Sent: Tuesday, April 05, 2016 11:33 PM
-To: James Thomas
-Cc: genivi-meta-ivi@lists.genivi.org
-Subject: Re: [meta-ivi] Building with local source mirror
-
-On Tue, Mar 29, 2016 at 10:51 PM, James Thomas <james.thomas@codethink.co.uk> wrote:
-> One thing I noticed is that simply providing the SRCREV works as long
-> as that sha exists within master, if it doesn't then you have a build
-> error, so being able to use tags is useful.
->
-> I think using git://...;tag=foo is not sufficient, because tags *can*
-> change (i.e there's no guarantee that the tag you're using is going to
-> be the same as the one you used yesterday).
->
-> What would be nice is if you could go tag=foo, and have it verified
-> against SRCREV (in my testing this resulted in a build error *when*
-> the tag and sha matched)
->
-> However, something like
->
-> SRC_URI = "git://mygitrepo/foo.git;nobranch=1;branch=v0.2"
-> SRCREV = "7654321"
->
-> does enforce that check (v0.2 is actually a tag in this case), which
-> seems to be pretty useful (the recipe provides something human
-> readable, and something a machine can understand, and will always
-> check they match)
-
-I completely understand the reasoning behind this. The point I'm trying to make is that the automotive industry has a strong need for reproducible offline builds and any kind of mandatory online checks break this requirement. And like Federico said, using SRCREV is also the Yocto project practice.
-
-If we want meta-ivi to be widely used in the industry I believe it should support it's needs. In my opinion the same should go for the whole GENIVI stack to work nicely, which in particular means tags of the projects should not change. But the easiest solution would be for meta-ivi to not use tags. That way it supports offline builds and it is also possible to track bugfixes in the projects instead of pinning to the tag and then getting the bugfixes in patch by patch until next release.
-
-How do the others on this list feel about this proposal?
-
-Regards,
---
-Igor Socec
-Software Engineer
-
-