Skip to contentSkip to conversation

tisdk-rootfs-base-image: Rename base file system image

PATCH In review Franklin S. Cooper Jr 3 participants 21 messages Sep 17, 2013 – Sep 26, 2013

lore
Share & tools
lore
#0 lore raw

PATCH 1/2 tisdk-rootfs-base-image: Rename base file system image

* People are frequently confused by the difference in naming between the minimal file system and the larger file system.
* Rename the minimal file system to mimic the naming convention of the larger file system.

---
 ...e-tisdk-image.bb => tisdk-rootfs-base-image.bb} |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
 rename meta-arago-distro/recipes-core/images/{arago-base-tisdk-image.bb => tisdk-rootfs-base-image.bb} (87%)
meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb +1 -1
similarity index 87%
rename from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb
rename to meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb
index 2c0e217..a3a9123 100644
@@ -12,4 +12,4 @@ IMAGE_INSTALL += "\
     packagegroup-arago-base-tisdk \
     "
 
-export IMAGE_BASENAME = "arago-base-tisdk-image"
+export IMAGE_BASENAME = "tisdk-rootfs-base-image"
Signature · 1 line
1.7.0.4
#1 lore raw

PATCH 2/2 Use updated base image name

* Change references from arago-base-tisdk-image to tisdk-rootfs-base-image to match updated image name.

---
 meta-arago-distro/classes/tisdk-image.bbclass      |    2 +-
 .../recipes-core/images/arago-core-tisdk-image.inc |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
meta-arago-distro/classes/tisdk-image.bbclass +1 -1
index 4397a70..1ccd2cd 100644
@@ -28,7 +28,7 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
 # List of target side images to be built and packaged.  By default take
 # the base image but this can be modified if desired to package
 # additional images.
-TARGET_IMAGES ?= "arago-base-tisdk-image"
+TARGET_IMAGES ?= "tisdk-rootfs-base-image"
 
 # path to install the meta-toolchain package in the SDK
 TISDK_TOOLCHAIN_PATH ?= "linux-devkit"
meta-arago-distro/recipes-core/images/arago-core-tisdk-image.inc +1 -1
index 1d00117..aaf2742 100644
@@ -22,7 +22,7 @@ DTB_FILTER_omap5-evm = "omap5"
 DTB_FILTER_dra7xx-evm = "dra7"
 
 # List of target side images to build for the SDK
-TARGET_IMAGES = "arago-base-tisdk-image tisdk-rootfs-image"
+TARGET_IMAGES = "tisdk-rootfs-base-image tisdk-rootfs-image"
 
 TISDK_TOOLCHAIN = "meta-toolchain-arago-tisdk"
 
Signature · 1 line
1.7.0.4
#2 lore raw
In reply to Franklin S. Cooper Jr

What was the initial reason to start naming rootfs images with tisdk-rootfs- prefix? I remember it was something forced by the SDK setup...

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 17, 2013 3:13 PM
To: [email protected]
Cc: Cooper Jr., Franklin
Subject: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

* People are frequently confused by the difference in naming between the minimal file system and the larger file system.
* Rename the minimal file system to mimic the naming convention of the larger file system.

---
 ...e-tisdk-image.bb => tisdk-rootfs-base-image.bb} |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)  rename meta-arago-distro/recipes-core/images/{arago-base-tisdk-image.bb => tisdk-rootfs-base-image.bb} (87%)
meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb +1 -1
similarity index 87%
rename from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb
rename to meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb
index 2c0e217..a3a9123 100644
@@ -12,4 +12,4 @@ IMAGE_INSTALL += "\
     packagegroup-arago-base-tisdk \
     "
 
-export IMAGE_BASENAME = "arago-base-tisdk-image"
+export IMAGE_BASENAME = "tisdk-rootfs-base-image"

--
1.7.0.4

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#3 lore raw
Quoted 11 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 17, 2013 2:52 PM
To: Cooper Jr., Franklin; [email protected]
Subject: RE: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

What was the initial reason to start naming rootfs images with tisdk-rootfs- prefix? I remember it was something forced by the SDK setup...

[Franklin]
This was before my time so I am not sure what the original reasoning was.

I do assume there might be instances where some script somewhere will need to be updated if it refers to the full image as "tisdk-rootfs*"

Quoted 46 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 17, 2013 3:13 PM
To: [email protected]
Cc: Cooper Jr., Franklin
Subject: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

* People are frequently confused by the difference in naming between the minimal
file system and the larger file system.
* Rename the minimal file system to mimic the naming convention of the larger file system.

---
 ...e-tisdk-image.bb => tisdk-rootfs-base-image.bb} |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)  rename meta-arago-

distro/recipes-core/images/{arago-base-tisdk-image.bb => tisdk-rootfs-base- image.bb} (87%)

meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk- +0 -0
similarity index 87%
rename from meta-arago-distro/recipes-core/images/arago-base-tisdk-

image.bb
rename to meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb index 2c0e217..a3a9123 100644

meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb +1 -2
@@ -12,4 +12,4 @@ IMAGE_INSTALL += "\
     packagegroup-arago-base-tisdk \
     "
 
-export IMAGE_BASENAME = "arago-base-tisdk-image"
+export IMAGE_BASENAME = "tisdk-rootfs-base-image"
--

1.7.0.4

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#4 lore raw
Quoted 9 lines · Franklin
Quoted 9 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 17, 2013 2:52 PM
To: Cooper Jr., Franklin; [email protected]
Subject: RE: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

Quoted 7 lines
Quoted 2 lines

What was the initial reason to start naming rootfs images with tisdk-rootfs- prefix? I remember it was something forced by the SDK setup...

[Franklin]
This was before my time so I am not sure what the original reasoning was.

I do assume there might be instances where some script somewhere will need to be updated if it refers to the full image as "tisdk-rootfs*"

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2c

The "tisdk-image class had issues" is a rather vague description, so I'm not sure or don't remember what was the problem that you had to rename the original arago-tisdk-image into tisdk-rootfs-image...

Signature · 1 line
Denys
Quoted 44 lines
Quoted 44 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 17, 2013 3:13 PM
To: [email protected]
Cc: Cooper Jr., Franklin
Subject: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

* People are frequently confused by the difference in naming between the minimal
file system and the larger file system.
* Rename the minimal file system to mimic the naming convention of the larger file system.

---
 ...e-tisdk-image.bb => tisdk-rootfs-base-image.bb} |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)  rename meta-arago-

distro/recipes-core/images/{arago-base-tisdk-image.bb => tisdk-rootfs-base- image.bb} (87%)

meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk- +0 -0
similarity index 87%
rename from meta-arago-distro/recipes-core/images/arago-base-tisdk-

image.bb
rename to meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb index 2c0e217..a3a9123 100644

meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb +1 -2
@@ -12,4 +12,4 @@ IMAGE_INSTALL += "\
     packagegroup-arago-base-tisdk \
     "
 
-export IMAGE_BASENAME = "arago-base-tisdk-image"
+export IMAGE_BASENAME = "tisdk-rootfs-base-image"
--

1.7.0.4

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#5 lore raw
Quoted 28 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Friday, September 20, 2013 2:31 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

Quoted 9 lines · Franklin
Quoted 9 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 17, 2013 2:52 PM
To: Cooper Jr., Franklin; [email protected]
Subject: RE: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 7 lines
Quoted 2 lines

What was the initial reason to start naming rootfs images with tisdk-rootfs- prefix? I remember it was something forced by the SDK setup...

[Franklin]
This was before my time so I am not sure what the original reasoning was.

I do assume there might be instances where some script somewhere will need to be updated if it refers to the full image as "tisdk-rootfs*"

Quoted 8 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-
arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2c

The "tisdk-image class had issues" is a rather vague description, so I'm not sure or don't remember what was the problem that you had to rename the original arago-tisdk-image into tisdk-rootfs-image...

[Franklin] Ah I remember. The TARGET_IMAGES variable is used in two ways in that class. 1 to add a build dependency and 2 to reference the image tarball. So the assumption was that the recipe/package name was the same as the IMAGE_BASENAME. So the recipe and IMAGE_BASENAME must match. Otherwise the image would be built but the class wouldn't know what tarball to look for.

Quoted 53 lines

--
Denys

Quoted 7 lines
Quoted 7 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 17, 2013 3:13 PM
To: [email protected]
Cc: Cooper Jr., Franklin
Subject: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base

file

Quoted 6 lines
Quoted 6 lines

system image

* People are frequently confused by the difference in naming between the minimal
file system and the larger file system.
* Rename the minimal file system to mimic the naming convention of the

larger

Quoted 7 lines
Quoted 7 lines

file system.

---
 ...e-tisdk-image.bb => tisdk-rootfs-base-image.bb} |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)  rename meta-arago-

distro/recipes-core/images/{arago-base-tisdk-image.bb => tisdk-rootfs-

base-

Quoted 3 lines

Review

Quoted 3 lines

image.bb} (87%)

(quoted diff) +0 -0

image.bb

Quoted 5 lines
Quoted 5 lines

b/meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb similarity index 87%
rename from meta-arago-distro/recipes-core/images/arago-base-tisdk- image.bb
rename to meta-arago-distro/recipes-core/images/tisdk-rootfs-base-

image.bb

Quoted 16 lines
Quoted 16 lines

index 2c0e217..a3a9123 100644

meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb +1 -2
@@ -12,4 +12,4 @@ IMAGE_INSTALL += "\
     packagegroup-arago-base-tisdk \
     "
 
-export IMAGE_BASENAME = "arago-base-tisdk-image"
+export IMAGE_BASENAME = "tisdk-rootfs-base-image"
--

1.7.0.4

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#6 lore raw
Quoted 37 lines · Franklin
Quoted 28 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Friday, September 20, 2013 2:31 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

Quoted 9 lines · Franklin
Quoted 9 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 17, 2013 2:52 PM
To: Cooper Jr., Franklin; [email protected]
Subject: RE: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 7 lines
Quoted 2 lines

What was the initial reason to start naming rootfs images with tisdk-rootfs- prefix? I remember it was something forced by the SDK setup...

[Franklin]
This was before my time so I am not sure what the original reasoning was.

I do assume there might be instances where some script somewhere will need to be updated if it refers to the full image as "tisdk-rootfs*"

Quoted 8 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-
arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2c

The "tisdk-image class had issues" is a rather vague description, so I'm not sure or don't remember what was the problem that you had to rename the original arago-tisdk-image into tisdk-rootfs-image...

Quoted 6 lines

[Franklin] Ah I remember. The TARGET_IMAGES variable is used in two ways in that class. 1 to add a build dependency and 2 to reference the image tarball. So the assumption was that the recipe/package name was the same as the IMAGE_BASENAME. So the recipe and IMAGE_BASENAME must match. Otherwise the image would be built but the class wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for. Tracing even further back shows that you added the recipe to have IMAGE_BASENAME = "tisdk-rootfs":

http://arago-project.org/git/?p=meta-arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f16ec4a

Do you remember the reason for that? This image recipe was in Classic arago, but there it had the basename matching the recipe name. Wondering why the change?

Signature · 1 line
Denys
Quoted 49 lines
Quoted 49 lines
Quoted 7 lines
Quoted 7 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 17, 2013 3:13 PM
To: [email protected]
Cc: Cooper Jr., Franklin
Subject: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base

file

Quoted 6 lines
Quoted 6 lines

system image

* People are frequently confused by the difference in naming between the minimal
file system and the larger file system.
* Rename the minimal file system to mimic the naming convention of the

larger

Quoted 7 lines
Quoted 7 lines

file system.

---
 ...e-tisdk-image.bb => tisdk-rootfs-base-image.bb} |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)  rename meta-arago-

distro/recipes-core/images/{arago-base-tisdk-image.bb => tisdk-rootfs-

base-

Quoted 3 lines

Review

Quoted 3 lines

image.bb} (87%)

(quoted diff) +0 -0

image.bb

Quoted 5 lines
Quoted 5 lines

b/meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb similarity index 87%
rename from meta-arago-distro/recipes-core/images/arago-base-tisdk- image.bb
rename to meta-arago-distro/recipes-core/images/tisdk-rootfs-base-

image.bb

Quoted 16 lines
Quoted 16 lines

index 2c0e217..a3a9123 100644

meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb +1 -2
@@ -12,4 +12,4 @@ IMAGE_INSTALL += "\
     packagegroup-arago-base-tisdk \
     "
 
-export IMAGE_BASENAME = "arago-base-tisdk-image"
+export IMAGE_BASENAME = "tisdk-rootfs-base-image"
--

1.7.0.4

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#7 lore raw
Quoted 60 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Friday, September 20, 2013 3:19 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

Quoted 20 lines · Franklin
Quoted 20 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Friday, September 20, 2013 2:31 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 9 lines · Franklin
Quoted 9 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 17, 2013 2:52 PM
To: Cooper Jr., Franklin; [email protected]
Subject: RE: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

What was the initial reason to start naming rootfs images with tisdk-rootfs- prefix? I remember it was something forced by the SDK

setup...

Quoted 15 lines
Quoted 6 lines
Quoted 5 lines

[Franklin]
This was before my time so I am not sure what the original reasoning was.

I do assume there might be instances where some script somewhere will need to be updated if it refers to the full image as "tisdk-rootfs*"

Quoted 8 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-
arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2c

The "tisdk-image class had issues" is a rather vague description, so I'm not sure or don't remember what was the problem that you had to rename the original arago-tisdk-image into tisdk-rootfs-image...

Quoted 4 lines

[Franklin] Ah I remember. The TARGET_IMAGES variable is used in two ways in that class. 1 to add a build dependency and 2 to reference the image tarball. So the assumption was that the recipe/package name was the same as the IMAGE_BASENAME. So the recipe and IMAGE_BASENAME

must

Quoted 2 lines

match. Otherwise the image would be built but the class wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for. Tracing even further back shows that you added the recipe to have IMAGE_BASENAME = "tisdk-rootfs":

Quoted 6 lines

http://arago-project.org/git/?p=meta-
arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f16ec4a

Do you remember the reason for that? This image recipe was in Classic arago, but there it had the basename matching the recipe name. Wondering why the change?

[Franklin] I think I was simply trying to match the filesystem tarball with the name used in previous sdks. I am assuming that the SDK backend script that built the sdk renamed those filesystem files.
Looking at Sitara AMSDK 05.05.01 (last oe-classic based sdk) the two filesystem tarballs were named base-rootfs-am335x-evm.tar.gz and tisdk-rootfs-am335x-evm.tar.gz. During that time I was focused on just getting the filesystem working and wanted it to look like the output from previous sdks. I don't think I had any other reason.

Quoted 57 lines

--
Denys

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 17, 2013 3:13 PM
To: [email protected]
Cc: Cooper Jr., Franklin
Subject: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename

base

Quoted 4 lines
Quoted 4 lines

file

Quoted 3 lines
Quoted 3 lines

system image

* People are frequently confused by the difference in naming between

the

Quoted 21 lines
Quoted 21 lines
Quoted 3 lines
Quoted 3 lines

minimal
file system and the larger file system.
* Rename the minimal file system to mimic the naming convention of the

larger

Quoted 7 lines
Quoted 7 lines

file system.

---
 ...e-tisdk-image.bb => tisdk-rootfs-base-image.bb} |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)  rename meta-arago-

distro/recipes-core/images/{arago-base-tisdk-image.bb => tisdk-rootfs-

base-

Quoted 3 lines

Review

Quoted 3 lines

image.bb} (87%)

(quoted diff) +0 -0

image.bb

Quoted 5 lines
Quoted 5 lines

b/meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb similarity index 87%
rename from meta-arago-distro/recipes-core/images/arago-base-tisdk- image.bb
rename to meta-arago-distro/recipes-core/images/tisdk-rootfs-base-

Quoted 4 lines
Quoted 4 lines

image.bb

Quoted 3 lines

meta-arago-distro/recipes-core/images/tisdk-rootfs-base-

Quoted 3 lines

index 2c0e217..a3a9123 100644

meta-arago-distro/recipes-core/images/tisdk-rootfs-base- renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb +0 -0

image.bb

Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
meta-arago-distro/recipes-core/images/tisdk-rootfs-base- renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb +1 -2
@@ -12,4 +12,4 @@ IMAGE_INSTALL += "\
     packagegroup-arago-base-tisdk \
     "
 
-export IMAGE_BASENAME = "arago-base-tisdk-image"
+export IMAGE_BASENAME = "tisdk-rootfs-base-image"
--

1.7.0.4

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#8 lore raw
Quoted 67 lines · Franklin
Quoted 60 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Friday, September 20, 2013 3:19 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

Quoted 20 lines · Franklin
Quoted 20 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Friday, September 20, 2013 2:31 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 9 lines · Franklin
Quoted 9 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 17, 2013 2:52 PM
To: Cooper Jr., Franklin; [email protected]
Subject: RE: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

What was the initial reason to start naming rootfs images with tisdk-rootfs- prefix? I remember it was something forced by the SDK

setup...

Quoted 15 lines
Quoted 6 lines
Quoted 5 lines

[Franklin]
This was before my time so I am not sure what the original reasoning was.

I do assume there might be instances where some script somewhere will need to be updated if it refers to the full image as "tisdk-rootfs*"

Quoted 8 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-
arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2c

The "tisdk-image class had issues" is a rather vague description, so I'm not sure or don't remember what was the problem that you had to rename the original arago-tisdk-image into tisdk-rootfs-image...

Quoted 4 lines

[Franklin] Ah I remember. The TARGET_IMAGES variable is used in two ways in that class. 1 to add a build dependency and 2 to reference the image tarball. So the assumption was that the recipe/package name was the same as the IMAGE_BASENAME. So the recipe and IMAGE_BASENAME

must

Quoted 2 lines

match. Otherwise the image would be built but the class wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for. Tracing even further back shows that you added the recipe to have IMAGE_BASENAME = "tisdk-rootfs":

Quoted 6 lines

http://arago-project.org/git/?p=meta-
arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f16ec4a

Do you remember the reason for that? This image recipe was in Classic arago, but there it had the basename matching the recipe name. Wondering why the change?

Quoted 8 lines

[Franklin] I think I was simply trying to match the filesystem tarball with the name used in previous sdks. I am assuming that the SDK backend script that built the sdk renamed those filesystem files. Looking at Sitara AMSDK 05.05.01 (last oe-classic based sdk) the two filesystem tarballs were named base-rootfs-am335x-evm.tar.gz and tisdk-rootfs-am335x-evm.tar.gz. During that time I was focused on just getting the filesystem working and wanted it to look like the output from previous sdks. I don't think I had any other reason.

Thanks! Just wanted to check if there was some sort of requirement for that name change. If there is not, then we can look for a better names for full image as well as base image.

Should we look into unifying the names for other image recipes? Is tisdk-rootfs- the best base we can think of?

Signature · 1 line
Denys
Quoted 52 lines
Quoted 52 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 17, 2013 3:13 PM
To: [email protected]
Cc: Cooper Jr., Franklin
Subject: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename

base

Quoted 4 lines
Quoted 4 lines

file

Quoted 3 lines
Quoted 3 lines

system image

* People are frequently confused by the difference in naming between

the

Quoted 21 lines
Quoted 21 lines
Quoted 3 lines
Quoted 3 lines

minimal
file system and the larger file system.
* Rename the minimal file system to mimic the naming convention of the

larger

Quoted 7 lines
Quoted 7 lines

file system.

---
 ...e-tisdk-image.bb => tisdk-rootfs-base-image.bb} |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)  rename meta-arago-

distro/recipes-core/images/{arago-base-tisdk-image.bb => tisdk-rootfs-

base-

Quoted 3 lines

Review

Quoted 3 lines

image.bb} (87%)

(quoted diff) +0 -0

image.bb

Quoted 5 lines
Quoted 5 lines

b/meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb similarity index 87%
rename from meta-arago-distro/recipes-core/images/arago-base-tisdk- image.bb
rename to meta-arago-distro/recipes-core/images/tisdk-rootfs-base-

Quoted 4 lines
Quoted 4 lines

image.bb

Quoted 3 lines

meta-arago-distro/recipes-core/images/tisdk-rootfs-base-

Quoted 3 lines

index 2c0e217..a3a9123 100644

meta-arago-distro/recipes-core/images/tisdk-rootfs-base- renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb +0 -0

image.bb

Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
meta-arago-distro/recipes-core/images/tisdk-rootfs-base- renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb +1 -2
@@ -12,4 +12,4 @@ IMAGE_INSTALL += "\
     packagegroup-arago-base-tisdk \
     "
 
-export IMAGE_BASENAME = "arago-base-tisdk-image"
+export IMAGE_BASENAME = "tisdk-rootfs-base-image"
--

1.7.0.4

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#9 lore raw
Quoted 97 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Friday, September 20, 2013 4:14 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

Quoted 31 lines · Franklin
Quoted 31 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Friday, September 20, 2013 3:19 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 20 lines · Franklin
Quoted 20 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Friday, September 20, 2013 2:31 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 9 lines · Franklin
Quoted 9 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 17, 2013 2:52 PM
To: Cooper Jr., Franklin; [email protected]
Subject: RE: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

What was the initial reason to start naming rootfs images with
tisdk-rootfs- prefix? I remember it was something forced by the SDK

setup...

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

[Franklin]
This was before my time so I am not sure what the original reasoning

was.

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

I do assume there might be instances where some script somewhere will need to be updated if it refers to the full image as

"tisdk-rootfs*"

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

c

The "tisdk-image class had issues" is a rather vague description, so I'm not sure or don't remember what was the problem that you had to rename the original arago-tisdk-image into

tisdk-rootfs-image...

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 1 line

[Franklin] Ah I remember. The TARGET_IMAGES variable is used in two ways in that class. 1 to add a build dependency and 2 to reference the image tarball. So the assumption was that the recipe/package name was the same as the IMAGE_BASENAME. So the recipe and IMAGE_BASENAME

Quoted 6 lines
Quoted 6 lines

must

Quoted 2 lines

match. Otherwise the image would be built but the class wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for. Tracing even further back shows that you added the recipe to have IMAGE_BASENAME =

"tisdk-rootfs":

Quoted 8 lines
Quoted 7 lines

http://arago-project.org/git/?p=meta-
arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f16ec4a

Do you remember the reason for that? This image recipe was in Classic arago, but there it had the basename matching the recipe name. Wondering why the change?

Quoted 9 lines

[Franklin] I think I was simply trying to match the filesystem tarball with the name used in previous sdks. I am assuming that the SDK backend script that built the sdk renamed those filesystem files. Looking at Sitara AMSDK
05.05.01 (last oe-classic based sdk) the two filesystem tarballs were named base-rootfs-am335x-evm.tar.gz and tisdk-rootfs-am335x-evm.tar.gz. During that time I was focused on just getting the filesystem working and wanted it to look like the output from previous sdks. I don't think I had any other reason.

Quoted 6 lines

Thanks! Just wanted to check if there was some sort of requirement for that name change. If there is not, then we can look for a better names for full image as well as base image.

Should we look into unifying the names for other image recipes? Is tisdk-rootfs- the best base we can think of?

[Franklin] I think it's important to separate the "arago" images from the "sdk" images. I am currently ok with the naming convention we use for our current images minus the one I created this patch for :). But I'm open to suggestions.

Quoted 63 lines

--
Denys

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 17, 2013 3:13 PM
To: [email protected]
Cc: Cooper Jr., Franklin
Subject: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename

Quoted 5 lines
Quoted 5 lines

base

Quoted 4 lines
Quoted 4 lines

file

Quoted 3 lines
Quoted 3 lines

system image

* People are frequently confused by the difference in naming

between

Quoted 4 lines
Quoted 4 lines

the

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

minimal
file system and the larger file system.
* Rename the minimal file system to mimic the naming convention of

the

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

larger

Quoted 7 lines
Quoted 7 lines

file system.

---
 ...e-tisdk-image.bb => tisdk-rootfs-base-image.bb} |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)  rename meta-arago-

distro/recipes-core/images/{arago-base-tisdk-image.bb => tisdk-

rootfs-

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

base-

Quoted 3 lines

Review

Quoted 3 lines

image.bb} (87%)

(quoted diff) +0 -0

image.bb

Quoted 1 line
Quoted 1 line

b/meta-arago-distro/recipes-core/images/tisdk-rootfs-base-

image.bb

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

similarity index 87%
rename from meta-arago-distro/recipes-core/images/arago-base-

tisdk-

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines

image.bb
rename to meta-arago-distro/recipes-core/images/tisdk-rootfs-base-

image.bb

Quoted 2 lines
Quoted 2 lines

index 2c0e217..a3a9123 100644
--- a/meta-arago-distro/recipes-core/images/arago-base-tisdk-

image.bb

Quoted 15 lines
Quoted 15 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

+++ b/meta-arago-distro/recipes-core/images/tisdk-rootfs-base-

image.bb

Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
(quoted diff) +1 -2
@@ -12,4 +12,4 @@ IMAGE_INSTALL += "\
     packagegroup-arago-base-tisdk \
     "
 
-export IMAGE_BASENAME = "arago-base-tisdk-image"
+export IMAGE_BASENAME = "tisdk-rootfs-base-image"
--

1.7.0.4

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#10 lore raw
Quoted 101 lines · Franklin
Quoted 101 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Friday, September 20, 2013 4:14 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

Quoted 31 lines · Franklin
Quoted 31 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Friday, September 20, 2013 3:19 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 20 lines · Franklin
Quoted 20 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Friday, September 20, 2013 2:31 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 9 lines · Franklin
Quoted 9 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 17, 2013 2:52 PM
To: Cooper Jr., Franklin; [email protected]
Subject: RE: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

What was the initial reason to start naming rootfs images with
tisdk-rootfs- prefix? I remember it was something forced by the SDK

setup...

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

[Franklin]
This was before my time so I am not sure what the original reasoning

was.

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

I do assume there might be instances where some script somewhere will need to be updated if it refers to the full image as

"tisdk-rootfs*"

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

c

The "tisdk-image class had issues" is a rather vague description, so I'm not sure or don't remember what was the problem that you had to rename the original arago-tisdk-image into

tisdk-rootfs-image...

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 1 line

[Franklin] Ah I remember. The TARGET_IMAGES variable is used in two ways in that class. 1 to add a build dependency and 2 to reference the image tarball. So the assumption was that the recipe/package name was the same as the IMAGE_BASENAME. So the recipe and IMAGE_BASENAME

Quoted 6 lines
Quoted 6 lines

must

Quoted 2 lines

match. Otherwise the image would be built but the class wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for. Tracing even further back shows that you added the recipe to have IMAGE_BASENAME =

"tisdk-rootfs":

Quoted 8 lines
Quoted 7 lines

http://arago-project.org/git/?p=meta-
arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f16ec4a

Do you remember the reason for that? This image recipe was in Classic arago, but there it had the basename matching the recipe name. Wondering why the change?

Quoted 9 lines

[Franklin] I think I was simply trying to match the filesystem tarball with the name used in previous sdks. I am assuming that the SDK backend script that built the sdk renamed those filesystem files. Looking at Sitara AMSDK
05.05.01 (last oe-classic based sdk) the two filesystem tarballs were named base-rootfs-am335x-evm.tar.gz and tisdk-rootfs-am335x-evm.tar.gz. During that time I was focused on just getting the filesystem working and wanted it to look like the output from previous sdks. I don't think I had any other reason.

Thanks! Just wanted to check if there was some sort of requirement for that name change. If there is not, then we can look for a better names for full image as well as base image.

Quoted 7 lines
Quoted 2 lines

Should we look into unifying the names for other image recipes? Is tisdk-rootfs- the best base we can think of?

[Franklin] I think it's important to separate the "arago" images from the "sdk" images. I am currently ok with the naming convention we use for our current images minus the one I created this patch for :). But I'm open to suggestions.

I'm not really sure what do you mean by separating arago from sdk. Arago distro is becoming the SDK, the Core TISDK one, to be exact. Other SDK products can build on top with slight variations.

We can place more generic packagegroups and images into meta-arago-extras and keep TISDK specific ones in meta-arago-distro.

As of the naming convention - I'm not exactly married to the arago- prefix for the image recipes, it was just a historic tradition - arago-base-image, arago-console-image, etc. I'm Ok with tisdk- prefix, but "rootfs" part always felt slightly artificial to me, as it was forced from outside and in OE images are images and there's no need to call them rootfs.

Anyway, what I'm trying to say is that now is the perfect time to align on the naming convention for our images and we don't need to stick to any of the existing names...

Signature · 1 line
Denys
Quoted 58 lines
Quoted 58 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 17, 2013 3:13 PM
To: [email protected]
Cc: Cooper Jr., Franklin
Subject: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename

Quoted 5 lines
Quoted 5 lines

base

Quoted 4 lines
Quoted 4 lines

file

Quoted 3 lines
Quoted 3 lines

system image

* People are frequently confused by the difference in naming

between

Quoted 4 lines
Quoted 4 lines

the

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

minimal
file system and the larger file system.
* Rename the minimal file system to mimic the naming convention of

the

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

larger

Quoted 7 lines
Quoted 7 lines

file system.

---
 ...e-tisdk-image.bb => tisdk-rootfs-base-image.bb} |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)  rename meta-arago-

distro/recipes-core/images/{arago-base-tisdk-image.bb => tisdk-

rootfs-

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

base-

Quoted 3 lines

Review

Quoted 3 lines

image.bb} (87%)

(quoted diff) +0 -0

image.bb

Quoted 1 line
Quoted 1 line

b/meta-arago-distro/recipes-core/images/tisdk-rootfs-base-

image.bb

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

similarity index 87%
rename from meta-arago-distro/recipes-core/images/arago-base-

tisdk-

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines

image.bb
rename to meta-arago-distro/recipes-core/images/tisdk-rootfs-base-

image.bb

Quoted 2 lines
Quoted 2 lines

index 2c0e217..a3a9123 100644
--- a/meta-arago-distro/recipes-core/images/arago-base-tisdk-

image.bb

Quoted 15 lines
Quoted 15 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

+++ b/meta-arago-distro/recipes-core/images/tisdk-rootfs-base-

image.bb

Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
(quoted diff) +1 -2
@@ -12,4 +12,4 @@ IMAGE_INSTALL += "\
     packagegroup-arago-base-tisdk \
     "
 
-export IMAGE_BASENAME = "arago-base-tisdk-image"
+export IMAGE_BASENAME = "tisdk-rootfs-base-image"
--

1.7.0.4

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#11 lore raw
Quoted 81 lines · Denys Dmytriyenko
Quoted 59 lines · Franklin
Quoted 59 lines
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

What was the initial reason to start naming rootfs images with
tisdk-rootfs- prefix? I remember it was something forced by the SDK

setup...

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

[Franklin]
This was before my time so I am not sure what the original reasoning

was.

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

I do assume there might be instances where some script somewhere will need to be updated if it refers to the full image as

"tisdk-rootfs*"

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

c

The "tisdk-image class had issues" is a rather vague description, so I'm not sure or don't remember what was the problem that you had to rename the original arago-tisdk-image into

tisdk-rootfs-image...

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 1 line

[Franklin] Ah I remember. The TARGET_IMAGES variable is used in two ways in that class. 1 to add a build dependency and 2 to reference the image tarball. So the assumption was that the recipe/package name was the same as the IMAGE_BASENAME. So the recipe and IMAGE_BASENAME

Quoted 6 lines
Quoted 6 lines

must

Quoted 2 lines

match. Otherwise the image would be built but the class wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for. Tracing even further back shows that you added the recipe to have IMAGE_BASENAME =

"tisdk-rootfs":

Quoted 8 lines
Quoted 7 lines

http://arago-project.org/git/?p=meta-
arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f16ec4a

Do you remember the reason for that? This image recipe was in Classic arago, but there it had the basename matching the recipe name. Wondering why the change?

Quoted 9 lines

[Franklin] I think I was simply trying to match the filesystem tarball with the name used in previous sdks. I am assuming that the SDK backend script that built the sdk renamed those filesystem files. Looking at Sitara AMSDK
05.05.01 (last oe-classic based sdk) the two filesystem tarballs were named base-rootfs-am335x-evm.tar.gz and tisdk-rootfs-am335x-evm.tar.gz. During that time I was focused on just getting the filesystem working and wanted it to look like the output from previous sdks. I don't think I had any other reason.

Thanks! Just wanted to check if there was some sort of requirement for that name change. If there is not, then we can look for a better names for full image as well as base image.

Quoted 7 lines
Quoted 2 lines

Should we look into unifying the names for other image recipes? Is tisdk-rootfs- the best base we can think of?

[Franklin] I think it's important to separate the "arago" images from the "sdk" images. I am currently ok with the naming convention we use for our current images minus the one I created this patch for :). But I'm open to suggestions.

I'm not really sure what do you mean by separating arago from sdk. Arago distro is becoming the SDK, the Core TISDK one, to be exact. Other SDK products can build on top with slight variations.

We can place more generic packagegroups and images into meta-arago-extras and keep TISDK specific ones in meta-arago-distro.

As of the naming convention - I'm not exactly married to the arago- prefix for the image recipes, it was just a historic tradition - arago-base-image, arago-console-image, etc. I'm Ok with tisdk- prefix, but "rootfs" part always felt slightly artificial to me, as it was forced from outside and in OE images are images and there's no need to call them rootfs.

Quoted 3 lines

Anyway, what I'm trying to say is that now is the perfect time to align on the naming convention for our images and we don't need to stick to any of the existing names...

Franklin,

Can you think of a unified naming for all the images, including base and full tisdk, as well as less common console and test images, that is scalable enough. As I'm thinking going back to arago-base-image and arago-tisdk-image vs. simplifying it to tisdk-base-image and tisdk-full-image. Plus it has to work with your other packagegroup restructure proposal... :)

Signature · 1 line
Denys
#12 lore raw
Quoted 103 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 24, 2013 2:52 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

Quoted 14 lines · Denys Dmytriyenko
Quoted 13 lines · Franklin
Quoted 13 lines
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

What was the initial reason to start naming rootfs images with
tisdk-rootfs- prefix? I remember it was something forced by the SDK

setup...

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

[Franklin]
This was before my time so I am not sure what the
original reasoning

was.

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

I do assume there might be instances where some script somewhere will need to be updated if it refers to the full image as

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

"tisdk-rootfs*"

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2

Quoted 57 lines
Quoted 45 lines
Quoted 45 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

c

The "tisdk-image class had issues" is a rather vague description, so I'm not sure or don't remember what was the problem that you had to rename the original arago-tisdk-image into

tisdk-rootfs-image...

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 1 line

[Franklin] Ah I remember. The TARGET_IMAGES variable is used in two ways in that class. 1 to add a build dependency and 2 to reference the image tarball. So the assumption was that the recipe/package name was the same as the IMAGE_BASENAME. So the recipe and IMAGE_BASENAME

Quoted 7 lines
Quoted 7 lines

must

Quoted 2 lines

match. Otherwise the image would be built but the class wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for. Tracing even further back shows that you added the recipe to have IMAGE_BASENAME =

"tisdk-rootfs":

Quoted 9 lines
Quoted 8 lines

http://arago-project.org/git/?p=meta-
arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f16e c4a

Do you remember the reason for that? This image recipe was in Classic arago, but there it had the basename matching the recipe name. Wondering why the change?

Quoted 9 lines

[Franklin] I think I was simply trying to match the filesystem tarball with the name used in previous sdks. I am assuming that the SDK backend script that built the sdk renamed those filesystem files. Looking at Sitara AMSDK
05.05.01 (last oe-classic based sdk) the two filesystem tarballs were named base-rootfs-am335x-evm.tar.gz and tisdk-rootfs-am335x-evm.tar.gz. During that time I was focused on just getting the filesystem working and wanted it to look like the output from previous sdks. I don't think I had any other reason.

Thanks! Just wanted to check if there was some sort of requirement for that name change. If there is not, then we can look for a better names for full image as well as base image.

Quoted 7 lines
Quoted 2 lines

Should we look into unifying the names for other image recipes? Is tisdk-rootfs- the best base we can think of?

[Franklin] I think it's important to separate the "arago" images from the "sdk" images. I am currently ok with the naming convention we use for our current images minus the one I created this patch for :). But I'm open to suggestions.

I'm not really sure what do you mean by separating arago from sdk. Arago distro is becoming the SDK, the Core TISDK one, to be exact. Other SDK products can build on top with slight variations.

Quoted 8 lines

We can place more generic packagegroups and images into meta-arago-extras and keep TISDK specific ones in meta-arago-distro.

As of the naming convention - I'm not exactly married to the arago- prefix for the image recipes, it was just a historic tradition - arago-base-image, arago-console-image, etc. I'm Ok with tisdk- prefix, but "rootfs" part always felt slightly artificial to me, as it was forced from outside and in OE images are images and there's no need to call

them rootfs.

Quoted 4 lines

Anyway, what I'm trying to say is that now is the perfect time to align on the naming convention for our images and we don't need to stick to any of the existing names...

Quoted 7 lines

Franklin,

Can you think of a unified naming for all the images, including base and full tisdk, as well as less common console and test images, that is scalable enough. As I'm thinking going back to arago-base-image and arago-tisdk-image vs. simplifying it to tisdk-base-image and tisdk-full-image. Plus it has to work with your other packagegroup restructure proposal... :)

[Franklin]

How about the following:

tisdk-rootfs-base-image -> arago-full-image ( me new proposed image)

tisdk-rootfs-image -> arago-full-sdk-image arago-base-tisdk-image -> arago-base-sdk-image arago-core-tisdk-image -> arago-core-sdk-image Tisdk-server-rootfs-image -> arago-server-sdk-image

Since our images are in meta-arago-distro which is dependent on meta-ti I think we could drop the "ti" from the image name to make it simpler. Based on the above logic I would probably change our packagegroups from using tisdk and simply call it sdk.
But if anyone has an issue I am ok with keeping tisdk in the packagegroups and images name.

Quoted 3 lines

--
Denys

#13 lore raw
Quoted 164 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 24, 2013 3:10 PM
To: Dmytriyenko, Denys
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 6 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 24, 2013 2:52 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:

Rename base

Quoted 3 lines

file system image

On Mon, Sep 23, 2013 at 11:34:44AM -0400, Denys Dmytriyenko

Quoted 1 line · wrote:
Quoted 1 line

On Mon, Sep 23, 2013 at 10:53:54AM -0400, Cooper Jr., Franklin

Quoted 1 line · wrote:
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

What was the initial reason to start naming

rootfs

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

images with
tisdk-rootfs- prefix? I remember it was

something

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

forced by the SDK

setup...

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

[Franklin]
This was before my time so I am not sure what

the

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

original reasoning

was.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

I do assume there might be instances where some

script

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

somewhere will need to be updated if it refers

to the

Quoted 11 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

full image as

"tisdk-rootfs*"

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

c

The "tisdk-image class had issues" is a rather

vague

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

description, so I'm not sure or don't remember

what was

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

the problem that you had to rename the original
arago-tisdk-image into

tisdk-rootfs-image...

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

[Franklin] Ah I remember. The TARGET_IMAGES variable

is used

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

in two ways in that class. 1 to add a build

dependency and 2

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

to reference the image tarball. So the assumption

was that

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

the recipe/package name was the same as the

IMAGE_BASENAME.

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

So the recipe and IMAGE_BASENAME

must

Quoted 1 line

match. Otherwise the image would be built but the

class

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for.

Tracing

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

even further back shows that you added the recipe to

have

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 1 line
Quoted 1 line

IMAGE_BASENAME =

"tisdk-rootfs":

Quoted 3 lines
Quoted 3 lines

http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f16e

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

c4a

Do you remember the reason for that? This image recipe

was in

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Classic arago, but there it had the basename matching

the

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

recipe name. Wondering why the change?

[Franklin] I think I was simply trying to match the

filesystem

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

tarball with the name used in previous sdks. I am

assuming that

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

the SDK backend script that built the sdk renamed those

filesystem files.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Looking at Sitara AMSDK
05.05.01 (last oe-classic based sdk) the two filesystem

tarballs

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

were named base-rootfs-am335x-evm.tar.gz and tisdk-rootfs-am335x-evm.tar.gz. During that time I was

focused

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

on just getting the filesystem working and wanted it to

look

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

like the output from previous sdks. I don't think I had

any other reason.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Thanks! Just wanted to check if there was some sort of

requirement

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

for that name change. If there is not, then we can look

for a

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

better names for full image as well as base image.

Should we look into unifying the names for other image

recipes? Is

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

tisdk-rootfs- the best base we can think of?

[Franklin] I think it's important to separate the "arago"

images

Quoted 1 line
Quoted 1 line
Quoted 1 line

from the "sdk" images. I am currently ok with the naming

convention

Quoted 1 line
Quoted 1 line
Quoted 1 line

we use for our current images minus the one I created this

patch for

Quoted 3 lines
Quoted 3 lines
Quoted 1 line

:). But I'm open to suggestions.

I'm not really sure what do you mean by separating arago from

sdk.

Quoted 1 line
Quoted 1 line

Arago distro is becoming the SDK, the Core TISDK one, to be

exact.

Quoted 4 lines
Quoted 4 lines

Other SDK products can build on top with slight variations.

We can place more generic packagegroups and images into meta-arago-extras and keep TISDK specific ones in meta-arago-

distro.

Quoted 2 lines
Quoted 2 lines

As of the naming convention - I'm not exactly married to the

arago-

Quoted 1 line
Quoted 1 line

prefix for the image recipes, it was just a historic tradition

-

Quoted 1 line
Quoted 1 line

arago-base-image, arago-console-image, etc. I'm Ok with tisdk-

prefix,

Quoted 1 line
Quoted 1 line

but "rootfs" part always felt slightly artificial to me, as it

was

Quoted 1 line
Quoted 1 line

forced from outside and in OE images are images and there's no

need to call

Quoted 3 lines

them rootfs.

Quoted 2 lines

Anyway, what I'm trying to say is that now is the perfect time

to

Quoted 1 line
Quoted 1 line

align on the naming convention for our images and we don't

need to

Quoted 5 lines
Quoted 1 line

stick to any of the existing names...

Franklin,

Can you think of a unified naming for all the images, including

base and full

Quoted 1 line

tisdk, as well as less common console and test images, that is

scalable enough. As

Quoted 1 line

I'm thinking going back to arago-base-image and arago-tisdk-

image vs.

Quoted 1 line

simplifying it to tisdk-base-image and tisdk-full-image. Plus it

Quoted 8 lines

has to work with

Quoted 1 line

your other packagegroup restructure proposal... :)

[Franklin]

How about the following:

tisdk-rootfs-base-image -> arago-full-image ( me new proposed image)

What will this image contain?

Quoted 2 lines

tisdk-rootfs-image -> arago-full-sdk-image

I want to differentiate between rootfs vs. sdk images. So maybe this one is arago-sdk-full-rootfs-image

Quoted 1 line

arago-base-tisdk-image -> arago-base-sdk-image

arago-sdk-base-rootfs-image

Quoted 1 line

arago-core-tisdk-image -> arago-core-sdk-image

Keep the same

Quoted 1 line

Tisdk-server-rootfs-image -> arago-server-sdk-image

arago-sdk-server-rootfs-image

What do you think?

Quoted 16 lines

Since our images are in meta-arago-distro which is dependent on meta-ti I think we could drop the "ti" from the image name to make it simpler.
Based on the above logic I would probably change our packagegroups from using tisdk and simply call it sdk.
But if anyone has an issue I am ok with keeping tisdk in the packagegroups and images name.

Quoted 3 lines

--
Denys

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#14 lore raw
Quoted 173 lines · Chase
Quoted 164 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 24, 2013 3:10 PM
To: Dmytriyenko, Denys
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 6 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 24, 2013 2:52 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:

Rename base

Quoted 3 lines

file system image

On Mon, Sep 23, 2013 at 11:34:44AM -0400, Denys Dmytriyenko

Quoted 1 line · wrote:
Quoted 1 line

On Mon, Sep 23, 2013 at 10:53:54AM -0400, Cooper Jr., Franklin

Quoted 1 line · wrote:
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

What was the initial reason to start naming

rootfs

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

images with
tisdk-rootfs- prefix? I remember it was

something

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

forced by the SDK

setup...

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

[Franklin]
This was before my time so I am not sure what

the

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

original reasoning

was.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

I do assume there might be instances where some

script

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

somewhere will need to be updated if it refers

to the

Quoted 11 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

full image as

"tisdk-rootfs*"

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

c

The "tisdk-image class had issues" is a rather

vague

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

description, so I'm not sure or don't remember

what was

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

the problem that you had to rename the original
arago-tisdk-image into

tisdk-rootfs-image...

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

[Franklin] Ah I remember. The TARGET_IMAGES variable

is used

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

in two ways in that class. 1 to add a build

dependency and 2

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

to reference the image tarball. So the assumption

was that

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

the recipe/package name was the same as the

IMAGE_BASENAME.

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

So the recipe and IMAGE_BASENAME

must

Quoted 1 line

match. Otherwise the image would be built but the

class

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for.

Tracing

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

even further back shows that you added the recipe to

have

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 1 line
Quoted 1 line

IMAGE_BASENAME =

"tisdk-rootfs":

Quoted 3 lines
Quoted 3 lines

http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f16e

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

c4a

Do you remember the reason for that? This image recipe

was in

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Classic arago, but there it had the basename matching

the

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

recipe name. Wondering why the change?

[Franklin] I think I was simply trying to match the

filesystem

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

tarball with the name used in previous sdks. I am

assuming that

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

the SDK backend script that built the sdk renamed those

filesystem files.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Looking at Sitara AMSDK
05.05.01 (last oe-classic based sdk) the two filesystem

tarballs

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

were named base-rootfs-am335x-evm.tar.gz and tisdk-rootfs-am335x-evm.tar.gz. During that time I was

focused

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

on just getting the filesystem working and wanted it to

look

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

like the output from previous sdks. I don't think I had

any other reason.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Thanks! Just wanted to check if there was some sort of

requirement

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

for that name change. If there is not, then we can look

for a

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

better names for full image as well as base image.

Should we look into unifying the names for other image

recipes? Is

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

tisdk-rootfs- the best base we can think of?

[Franklin] I think it's important to separate the "arago"

images

Quoted 1 line
Quoted 1 line
Quoted 1 line

from the "sdk" images. I am currently ok with the naming

convention

Quoted 1 line
Quoted 1 line
Quoted 1 line

we use for our current images minus the one I created this

patch for

Quoted 3 lines
Quoted 3 lines
Quoted 1 line

:). But I'm open to suggestions.

I'm not really sure what do you mean by separating arago from

sdk.

Quoted 1 line
Quoted 1 line

Arago distro is becoming the SDK, the Core TISDK one, to be

exact.

Quoted 4 lines
Quoted 4 lines

Other SDK products can build on top with slight variations.

We can place more generic packagegroups and images into meta-arago-extras and keep TISDK specific ones in meta-arago-

distro.

Quoted 2 lines
Quoted 2 lines

As of the naming convention - I'm not exactly married to the

arago-

Quoted 1 line
Quoted 1 line

prefix for the image recipes, it was just a historic tradition

-

Quoted 1 line
Quoted 1 line

arago-base-image, arago-console-image, etc. I'm Ok with tisdk-

prefix,

Quoted 1 line
Quoted 1 line

but "rootfs" part always felt slightly artificial to me, as it

was

Quoted 1 line
Quoted 1 line

forced from outside and in OE images are images and there's no

need to call

Quoted 3 lines

them rootfs.

Quoted 2 lines

Anyway, what I'm trying to say is that now is the perfect time

to

Quoted 1 line
Quoted 1 line

align on the naming convention for our images and we don't

need to

Quoted 5 lines
Quoted 1 line

stick to any of the existing names...

Franklin,

Can you think of a unified naming for all the images, including

base and full

Quoted 1 line

tisdk, as well as less common console and test images, that is

scalable enough. As

Quoted 1 line

I'm thinking going back to arago-base-image and arago-tisdk-

image vs.

Quoted 1 line

simplifying it to tisdk-base-image and tisdk-full-image. Plus it

Quoted 8 lines

has to work with

Quoted 1 line

your other packagegroup restructure proposal... :)

[Franklin]

How about the following:

tisdk-rootfs-base-image -> arago-full-image ( me new proposed image)

Quoted 7 lines

What will this image contain?

Quoted 2 lines

tisdk-rootfs-image -> arago-full-sdk-image

I want to differentiate between rootfs vs. sdk images. So maybe this one is arago-sdk-full-rootfs-image

Heh, I was the one who asked Franklin specifically to drop "rootfs" part... :) Please read the above explanation. For the most part, images are rootfs. But I see what you are saying - we now have these hybrid SDK images that contain other rootfs images, kernel/bootloader images and devkit(s). So, how about we clearly mark those instead of everything else with "rootfs"?

Quoted 30 lines
Quoted 1 line

arago-base-tisdk-image -> arago-base-sdk-image

arago-sdk-base-rootfs-image

Quoted 1 line

arago-core-tisdk-image -> arago-core-sdk-image

Keep the same

Quoted 1 line

Tisdk-server-rootfs-image -> arago-server-sdk-image

arago-sdk-server-rootfs-image

What do you think?

Quoted 16 lines

Since our images are in meta-arago-distro which is dependent on meta-ti I think we could drop the "ti" from the image name to make it simpler.
Based on the above logic I would probably change our packagegroups from using tisdk and simply call it sdk.
But if anyone has an issue I am ok with keeping tisdk in the packagegroups and images name.

Quoted 3 lines

--
Denys

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#15 lore raw
Quoted 217 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Thursday, September 26, 2013 2:52 PM
To: Maupin, Chase
Cc: Cooper Jr., Franklin; [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 11 lines · Chase
Quoted 11 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 24, 2013 3:10 PM
To: Dmytriyenko, Denys
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 24, 2013 2:52 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-

image:

Quoted 6 lines
Quoted 6 lines

Rename base

Quoted 3 lines

file system image

On Mon, Sep 23, 2013 at 11:34:44AM -0400, Denys Dmytriyenko

Quoted 1 line · wrote:
Quoted 1 line

On Mon, Sep 23, 2013 at 10:53:54AM -0400, Cooper Jr.,

Franklin

Quoted 7 lines
Quoted 7 lines
Quoted 1 line · wrote:
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

What was the initial reason to start naming

rootfs

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

images with
tisdk-rootfs- prefix? I remember it was

something

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

forced by the SDK

Quoted 8 lines
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

setup...

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

[Franklin]
This was before my time so I am not sure what

the

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

original reasoning

was.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

I do assume there might be instances where

some

Quoted 2 lines
Quoted 2 lines

script

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

somewhere will need to be updated if it

refers

Quoted 9 lines
Quoted 9 lines

to the

Quoted 8 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

full image as

"tisdk-rootfs*"

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2

Quoted 4 lines
Quoted 4 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

c

The "tisdk-image class had issues" is a rather

vague

Quoted 8 lines
Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

description, so I'm not sure or don't remember

what was

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

the problem that you had to rename the original
arago-tisdk-image into

tisdk-rootfs-image...

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

[Franklin] Ah I remember. The TARGET_IMAGES

variable

Quoted 8 lines
Quoted 8 lines

is used

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

in two ways in that class. 1 to add a build

dependency and 2

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

to reference the image tarball. So the assumption

was that

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

the recipe/package name was the same as the

IMAGE_BASENAME.

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

So the recipe and IMAGE_BASENAME

Quoted 8 lines
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

must

Quoted 1 line

match. Otherwise the image would be built but the

class

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for.

Tracing

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

even further back shows that you added the recipe

to

Quoted 10 lines
Quoted 10 lines

have

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 1 line
Quoted 1 line

IMAGE_BASENAME =

"tisdk-rootfs":

Quoted 3 lines
Quoted 3 lines

http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f16e

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

c4a

Do you remember the reason for that? This image

recipe

Quoted 2 lines
Quoted 2 lines

was in

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Classic arago, but there it had the basename

matching

Quoted 8 lines
Quoted 8 lines

the

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

recipe name. Wondering why the change?

[Franklin] I think I was simply trying to match the

filesystem

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

tarball with the name used in previous sdks. I am

assuming that

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

the SDK backend script that built the sdk renamed

those

Quoted 3 lines
Quoted 3 lines

filesystem files.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Looking at Sitara AMSDK
05.05.01 (last oe-classic based sdk) the two

filesystem

Quoted 3 lines
Quoted 3 lines

tarballs

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

were named base-rootfs-am335x-evm.tar.gz and tisdk-rootfs-am335x-evm.tar.gz. During that time I

was

Quoted 2 lines
Quoted 2 lines

focused

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

on just getting the filesystem working and wanted it

to

Quoted 2 lines
Quoted 2 lines

look

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

like the output from previous sdks. I don't think I

had

Quoted 9 lines
Quoted 9 lines

any other reason.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Thanks! Just wanted to check if there was some sort of

requirement

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

for that name change. If there is not, then we can look

for a

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

better names for full image as well as base image.

Should we look into unifying the names for other image

Quoted 8 lines
Quoted 8 lines

recipes? Is

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

tisdk-rootfs- the best base we can think of?

[Franklin] I think it's important to separate the "arago"

images

Quoted 1 line
Quoted 1 line
Quoted 1 line

from the "sdk" images. I am currently ok with the naming

convention

Quoted 1 line
Quoted 1 line
Quoted 1 line

we use for our current images minus the one I created

this

Quoted 4 lines
Quoted 4 lines

patch for

Quoted 3 lines
Quoted 3 lines
Quoted 1 line

:). But I'm open to suggestions.

I'm not really sure what do you mean by separating arago

from

Quoted 7 lines
Quoted 7 lines

sdk.

Quoted 1 line
Quoted 1 line

Arago distro is becoming the SDK, the Core TISDK one, to be

exact.

Quoted 4 lines
Quoted 4 lines

Other SDK products can build on top with slight variations.

We can place more generic packagegroups and images into meta-arago-extras and keep TISDK specific ones in meta-

arago-

Quoted 3 lines
Quoted 3 lines

distro.

Quoted 2 lines
Quoted 2 lines

As of the naming convention - I'm not exactly married to

the

Quoted 2 lines
Quoted 2 lines

arago-

Quoted 1 line
Quoted 1 line

prefix for the image recipes, it was just a historic

tradition

Quoted 2 lines
Quoted 2 lines

-

Quoted 1 line
Quoted 1 line

arago-base-image, arago-console-image, etc. I'm Ok with

tisdk-

Quoted 2 lines
Quoted 2 lines

prefix,

Quoted 1 line
Quoted 1 line

but "rootfs" part always felt slightly artificial to me, as

it

Quoted 2 lines
Quoted 2 lines

was

Quoted 1 line
Quoted 1 line

forced from outside and in OE images are images and there's

no

Quoted 4 lines
Quoted 4 lines

need to call

Quoted 3 lines

them rootfs.

Quoted 2 lines

Anyway, what I'm trying to say is that now is the perfect

time

Quoted 8 lines
Quoted 8 lines

to

Quoted 1 line
Quoted 1 line

align on the naming convention for our images and we don't

need to

Quoted 5 lines
Quoted 1 line

stick to any of the existing names...

Franklin,

Can you think of a unified naming for all the images,

including

Quoted 2 lines
Quoted 2 lines

base and full

Quoted 1 line

tisdk, as well as less common console and test images, that

is

Quoted 4 lines
Quoted 4 lines

scalable enough. As

Quoted 1 line

I'm thinking going back to arago-base-image and arago-tisdk-

image vs.

Quoted 1 line

simplifying it to tisdk-base-image and tisdk-full-image. Plus

it

Quoted 9 lines
Quoted 8 lines

has to work with

Quoted 1 line

your other packagegroup restructure proposal... :)

[Franklin]

How about the following:

tisdk-rootfs-base-image -> arago-full-image ( me new proposed image)

Quoted 6 lines

What will this image contain?

Quoted 2 lines

tisdk-rootfs-image -> arago-full-sdk-image

I want to differentiate between rootfs vs. sdk images. So maybe

this one is

Quoted 1 line

arago-sdk-full-rootfs-image

Quoted 9 lines

Heh, I was the one who asked Franklin specifically to drop "rootfs" part... :)
Please read the above explanation. For the most part, images are rootfs. But I
see what you are saying - we now have these hybrid SDK images that contain
other rootfs images, kernel/bootloader images and devkit(s). So, how about we
clearly mark those instead of everything else with "rootfs"?

That works too

Quoted 34 lines
Quoted 8 lines
Quoted 3 lines

arago-base-tisdk-image -> arago-base-sdk-image

arago-sdk-base-rootfs-image

Quoted 1 line

arago-core-tisdk-image -> arago-core-sdk-image

Quoted 11 lines

Keep the same

Quoted 1 line

Tisdk-server-rootfs-image -> arago-server-sdk-image

arago-sdk-server-rootfs-image

What do you think?

Quoted 3 lines

Since our images are in meta-arago-distro which is dependent on meta-ti I think we could drop the "ti" from the image name to

make

Quoted 2 lines
Quoted 2 lines

it simpler.
Based on the above logic I would probably change our

packagegroups

Quoted 11 lines
Quoted 11 lines

from using tisdk and simply call it sdk.
But if anyone has an issue I am ok with keeping tisdk in the packagegroups and images name.

Quoted 3 lines

--
Denys

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#16 lore raw
Quoted 196 lines · Chase
Quoted 196 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Thursday, September 26, 2013 2:52 PM
To: Maupin, Chase
Cc: Cooper Jr., Franklin; [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 11 lines · Chase
Quoted 11 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 24, 2013 3:10 PM
To: Dmytriyenko, Denys
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image:
Rename base file system image

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 24, 2013 2:52 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-

image:

Quoted 6 lines
Quoted 6 lines

Rename base

Quoted 3 lines

file system image

On Mon, Sep 23, 2013 at 11:34:44AM -0400, Denys Dmytriyenko

Quoted 1 line · wrote:
Quoted 1 line

On Mon, Sep 23, 2013 at 10:53:54AM -0400, Cooper Jr.,

Franklin

Quoted 7 lines
Quoted 7 lines
Quoted 1 line · wrote:
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

What was the initial reason to start naming

rootfs

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

images with
tisdk-rootfs- prefix? I remember it was

something

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

forced by the SDK

Quoted 8 lines
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

setup...

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

[Franklin]
This was before my time so I am not sure what

the

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

original reasoning

was.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

I do assume there might be instances where

some

Quoted 2 lines
Quoted 2 lines

script

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

somewhere will need to be updated if it

refers

Quoted 6 lines
Quoted 6 lines

to the

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

full image as

"tisdk-rootfs*"

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2

Quoted 11 lines
Quoted 11 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

c

The "tisdk-image class had issues" is a rather

vague

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

description, so I'm not sure or don't remember

what was

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

the problem that you had to rename the original
arago-tisdk-image into

tisdk-rootfs-image...

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

[Franklin] Ah I remember. The TARGET_IMAGES

variable

Quoted 8 lines
Quoted 8 lines

is used

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

in two ways in that class. 1 to add a build

dependency and 2

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

to reference the image tarball. So the assumption

was that

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

the recipe/package name was the same as the

IMAGE_BASENAME.

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

So the recipe and IMAGE_BASENAME

Quoted 8 lines
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

must

Quoted 1 line

match. Otherwise the image would be built but the

class

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for.

Tracing

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

even further back shows that you added the recipe

to

Quoted 9 lines
Quoted 9 lines

have

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line

IMAGE_BASENAME =

"tisdk-rootfs":

Quoted 2 lines
Quoted 2 lines

http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f16e

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

c4a

Do you remember the reason for that? This image

recipe

Quoted 2 lines
Quoted 2 lines

was in

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Classic arago, but there it had the basename

matching

Quoted 8 lines
Quoted 8 lines

the

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

recipe name. Wondering why the change?

[Franklin] I think I was simply trying to match the

filesystem

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

tarball with the name used in previous sdks. I am

assuming that

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

the SDK backend script that built the sdk renamed

those

Quoted 3 lines
Quoted 3 lines

filesystem files.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Looking at Sitara AMSDK
05.05.01 (last oe-classic based sdk) the two

filesystem

Quoted 3 lines
Quoted 3 lines

tarballs

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

were named base-rootfs-am335x-evm.tar.gz and tisdk-rootfs-am335x-evm.tar.gz. During that time I

was

Quoted 2 lines
Quoted 2 lines

focused

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

on just getting the filesystem working and wanted it

to

Quoted 2 lines
Quoted 2 lines

look

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

like the output from previous sdks. I don't think I

had

Quoted 9 lines
Quoted 9 lines

any other reason.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Thanks! Just wanted to check if there was some sort of

requirement

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

for that name change. If there is not, then we can look

for a

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

better names for full image as well as base image.

Should we look into unifying the names for other image

Quoted 8 lines
Quoted 8 lines

recipes? Is

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line

tisdk-rootfs- the best base we can think of?

[Franklin] I think it's important to separate the "arago"

images

Quoted 1 line
Quoted 1 line
Quoted 1 line

from the "sdk" images. I am currently ok with the naming

convention

Quoted 1 line
Quoted 1 line
Quoted 1 line

we use for our current images minus the one I created

this

Quoted 4 lines
Quoted 4 lines

patch for

Quoted 3 lines
Quoted 3 lines
Quoted 1 line

:). But I'm open to suggestions.

I'm not really sure what do you mean by separating arago

from

Quoted 7 lines
Quoted 7 lines

sdk.

Quoted 1 line
Quoted 1 line

Arago distro is becoming the SDK, the Core TISDK one, to be

exact.

Quoted 4 lines
Quoted 4 lines

Other SDK products can build on top with slight variations.

We can place more generic packagegroups and images into meta-arago-extras and keep TISDK specific ones in meta-

arago-

Quoted 3 lines
Quoted 3 lines

distro.

Quoted 2 lines
Quoted 2 lines

As of the naming convention - I'm not exactly married to

the

Quoted 2 lines
Quoted 2 lines

arago-

Quoted 1 line
Quoted 1 line

prefix for the image recipes, it was just a historic

tradition

Quoted 2 lines
Quoted 2 lines

-

Quoted 1 line
Quoted 1 line

arago-base-image, arago-console-image, etc. I'm Ok with

tisdk-

Quoted 2 lines
Quoted 2 lines

prefix,

Quoted 1 line
Quoted 1 line

but "rootfs" part always felt slightly artificial to me, as

it

Quoted 2 lines
Quoted 2 lines

was

Quoted 1 line
Quoted 1 line

forced from outside and in OE images are images and there's

no

Quoted 4 lines
Quoted 4 lines

need to call

Quoted 3 lines

them rootfs.

Quoted 2 lines

Anyway, what I'm trying to say is that now is the perfect

time

Quoted 8 lines
Quoted 8 lines

to

Quoted 1 line
Quoted 1 line

align on the naming convention for our images and we don't

need to

Quoted 5 lines
Quoted 1 line

stick to any of the existing names...

Franklin,

Can you think of a unified naming for all the images,

including

Quoted 2 lines
Quoted 2 lines

base and full

Quoted 1 line

tisdk, as well as less common console and test images, that

is

Quoted 4 lines
Quoted 4 lines

scalable enough. As

Quoted 1 line

I'm thinking going back to arago-base-image and arago-tisdk-

image vs.

Quoted 1 line

simplifying it to tisdk-base-image and tisdk-full-image. Plus

it

Quoted 2 lines
Quoted 2 lines

has to work with

Quoted 1 line

your other packagegroup restructure proposal... :)

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 6 lines

[Franklin]

How about the following:

tisdk-rootfs-base-image -> arago-full-image ( me new proposed image)

What will this image contain?

This contained everything that the below image contains minus SDK example applications, scripts and Matrix.

Quoted 18 lines
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

tisdk-rootfs-image -> arago-full-sdk-image

I want to differentiate between rootfs vs. sdk images. So maybe

this one is

Quoted 1 line

arago-sdk-full-rootfs-image

Quoted 9 lines

Heh, I was the one who asked Franklin specifically to drop "rootfs" part... :)
Please read the above explanation. For the most part, images are rootfs. But I
see what you are saying - we now have these hybrid SDK images that contain
other rootfs images, kernel/bootloader images and devkit(s). So, how about we
clearly mark those instead of everything else with "rootfs"?

Quoted 1 line

That works too

Overall I'm ok with this and Denys addressed the only comment I had.

Quoted 35 lines
Quoted 35 lines
Quoted 9 lines
Quoted 4 lines

arago-base-tisdk-image -> arago-base-sdk-image

arago-sdk-base-rootfs-image

Quoted 1 line

arago-core-tisdk-image -> arago-core-sdk-image

Quoted 11 lines

Keep the same

Quoted 1 line

Tisdk-server-rootfs-image -> arago-server-sdk-image

arago-sdk-server-rootfs-image

What do you think?

Quoted 3 lines

Since our images are in meta-arago-distro which is dependent on meta-ti I think we could drop the "ti" from the image name to

make

Quoted 2 lines
Quoted 2 lines

it simpler.
Based on the above logic I would probably change our

packagegroups

Quoted 11 lines
Quoted 11 lines

from using tisdk and simply call it sdk.
But if anyone has an issue I am ok with keeping tisdk in the packagegroups and images name.

Quoted 3 lines

--
Denys

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#17 lore raw
In reply to Denys Dmytriyenko
Quoted 136 lines

-----Original Message-----
From: Cooper Jr., Franklin
Sent: Tuesday, September 24, 2013 3:10 PM
To: Dmytriyenko, Denys
Cc: [email protected]
Subject: RE: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

Quoted 23 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 24, 2013 2:52 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

Quoted 14 lines · Denys Dmytriyenko
Quoted 13 lines · Franklin
Quoted 13 lines
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

What was the initial reason to start naming rootfs images with
tisdk-rootfs- prefix? I remember it was something forced by the SDK

setup...

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

[Franklin]
This was before my time so I am not sure what the
original reasoning

was.

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

I do assume there might be instances where some script somewhere will need to be updated if it refers to the full image as

Quoted 20 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

"tisdk-rootfs*"

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2

Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

c

The "tisdk-image class had issues" is a rather vague description, so I'm not sure or don't remember what was the problem that you had to rename the original arago-tisdk-image into

tisdk-rootfs-image...

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 1 line

[Franklin] Ah I remember. The TARGET_IMAGES variable is used in two ways in that class. 1 to add a build dependency and 2 to reference the image tarball. So the assumption was that the recipe/package name was the same as the

IMAGE_BASENAME.

Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 8 lines
Quoted 8 lines
Quoted 1 line

So the recipe and IMAGE_BASENAME

must

Quoted 2 lines

match. Otherwise the image would be built but the class wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for. Tracing even further back shows that you added the recipe to have IMAGE_BASENAME =

"tisdk-rootfs":

Quoted 6 lines
Quoted 6 lines

http://arago-project.org/git/?p=meta-
arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f1 6e
c4a

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 3 lines

Do you remember the reason for that? This image recipe was in Classic arago, but there it had the basename matching the recipe name. Wondering why the change?

[Franklin] I think I was simply trying to match the filesystem tarball with the name used in previous sdks. I am assuming that the SDK backend script that built the sdk renamed those filesystem

files.

Quoted 39 lines
Quoted 27 lines
Quoted 11 lines
Quoted 11 lines
Quoted 6 lines

Looking at Sitara AMSDK
05.05.01 (last oe-classic based sdk) the two filesystem tarballs were named base-rootfs-am335x-evm.tar.gz and tisdk-rootfs-am335x-evm.tar.gz. During that time I was focused on just getting the filesystem working and wanted it to look like the output from previous sdks. I don't think I had any other reason.

Thanks! Just wanted to check if there was some sort of requirement for that name change. If there is not, then we can look for a better names for full image as well as base image.

Quoted 8 lines
Quoted 3 lines

Should we look into unifying the names for other image recipes? Is
tisdk-rootfs- the best base we can think of?

[Franklin] I think it's important to separate the "arago" images from the "sdk" images. I am currently ok with the naming convention we use for our current images minus the one I created this patch for :). But I'm open to suggestions.

I'm not really sure what do you mean by separating arago from sdk. Arago distro is becoming the SDK, the Core TISDK one, to be exact. Other SDK products can build on top with slight variations.

We can place more generic packagegroups and images into meta-arago-extras and keep TISDK specific ones in meta-arago-distro.

Quoted 6 lines

As of the naming convention - I'm not exactly married to the arago- prefix for the image recipes, it was just a historic tradition - arago-base-image, arago-console-image, etc. I'm Ok with tisdk- prefix, but "rootfs" part always felt slightly artificial to me, as it was forced from outside and in OE images are images and there's no need to call

them rootfs.

Quoted 4 lines

Anyway, what I'm trying to say is that now is the perfect time to align on the naming convention for our images and we don't need to stick to any of the existing names...

Quoted 5 lines

Franklin,

Can you think of a unified naming for all the images, including base and full tisdk, as well as less common console and test images, that is scalable enough. As I'm thinking going back to arago-base-image and arago-

tisdk-image vs.

Quoted 2 lines

simplifying it to tisdk-base-image and tisdk-full-image. Plus it has to work with your other packagegroup restructure proposal... :)

[Franklin]

How about the following:

tisdk-rootfs-base-image -> arago-full-image ( me new proposed image)

tisdk-rootfs-image -> arago-full-sdk-image arago-base-tisdk-image -> arago- base-sdk-image arago-core-tisdk-image -> arago-core-sdk-image Tisdk-server- rootfs-image -> arago-server-sdk-image

Quoted 6 lines

Since our images are in meta-arago-distro which is dependent on meta-ti I think we could drop the "ti" from the image name to make it simpler. Based on the above logic I would probably change our packagegroups from using tisdk and simply call it sdk.
But if anyone has an issue I am ok with keeping tisdk in the packagegroups and images name.

[Franklin] Thoughts?

Quoted 4 lines
Quoted 4 lines

--
Denys

#18 lore raw
Quoted 136 lines · Franklin
Quoted 136 lines

-----Original Message-----
From: Cooper Jr., Franklin
Sent: Tuesday, September 24, 2013 3:10 PM
To: Dmytriyenko, Denys
Cc: [email protected]
Subject: RE: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

Quoted 23 lines

-----Original Message-----
From: Dmytriyenko, Denys
Sent: Tuesday, September 24, 2013 2:52 PM
To: Cooper Jr., Franklin
Cc: [email protected]
Subject: Re: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

Quoted 14 lines · Denys Dmytriyenko
Quoted 13 lines · Franklin
Quoted 13 lines
Quoted 8 lines
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

What was the initial reason to start naming rootfs images with
tisdk-rootfs- prefix? I remember it was something forced by the SDK

setup...

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

[Franklin]
This was before my time so I am not sure what the
original reasoning

was.

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

I do assume there might be instances where some script somewhere will need to be updated if it refers to the full image as

Quoted 20 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

"tisdk-rootfs*"

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

So, I located the change I was talking about:
http://arago-project.org/git/?p=meta-

arago.git;a=commitdiff;h=91f2be34e301deebbc75c54bbad6a5a27e25bf2

Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

c

The "tisdk-image class had issues" is a rather vague description, so I'm not sure or don't remember what was the problem that you had to rename the original arago-tisdk-image into

tisdk-rootfs-image...

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 1 line

[Franklin] Ah I remember. The TARGET_IMAGES variable is used in two ways in that class. 1 to add a build dependency and 2 to reference the image tarball. So the assumption was that the recipe/package name was the same as the

IMAGE_BASENAME.

Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 15 lines
Quoted 8 lines
Quoted 8 lines
Quoted 1 line

So the recipe and IMAGE_BASENAME

must

Quoted 2 lines

match. Otherwise the image would be built but the class wouldn't know what tarball to look for.

Ah, OK, this is not exactly what I was looking for. Tracing even further back shows that you added the recipe to have IMAGE_BASENAME =

"tisdk-rootfs":

Quoted 6 lines
Quoted 6 lines

http://arago-project.org/git/?p=meta-
arago.git;a=commitdiff;h=f27b1f34aee2c2cbee25a0fb5b21cdb04f1 6e
c4a

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 3 lines

Do you remember the reason for that? This image recipe was in Classic arago, but there it had the basename matching the recipe name. Wondering why the change?

[Franklin] I think I was simply trying to match the filesystem tarball with the name used in previous sdks. I am assuming that the SDK backend script that built the sdk renamed those filesystem

files.

Quoted 39 lines
Quoted 27 lines
Quoted 11 lines
Quoted 11 lines
Quoted 6 lines

Looking at Sitara AMSDK
05.05.01 (last oe-classic based sdk) the two filesystem tarballs were named base-rootfs-am335x-evm.tar.gz and tisdk-rootfs-am335x-evm.tar.gz. During that time I was focused on just getting the filesystem working and wanted it to look like the output from previous sdks. I don't think I had any other reason.

Thanks! Just wanted to check if there was some sort of requirement for that name change. If there is not, then we can look for a better names for full image as well as base image.

Quoted 8 lines
Quoted 3 lines

Should we look into unifying the names for other image recipes? Is
tisdk-rootfs- the best base we can think of?

[Franklin] I think it's important to separate the "arago" images from the "sdk" images. I am currently ok with the naming convention we use for our current images minus the one I created this patch for :). But I'm open to suggestions.

I'm not really sure what do you mean by separating arago from sdk. Arago distro is becoming the SDK, the Core TISDK one, to be exact. Other SDK products can build on top with slight variations.

We can place more generic packagegroups and images into meta-arago-extras and keep TISDK specific ones in meta-arago-distro.

Quoted 6 lines

As of the naming convention - I'm not exactly married to the arago- prefix for the image recipes, it was just a historic tradition - arago-base-image, arago-console-image, etc. I'm Ok with tisdk- prefix, but "rootfs" part always felt slightly artificial to me, as it was forced from outside and in OE images are images and there's no need to call

them rootfs.

Quoted 4 lines

Anyway, what I'm trying to say is that now is the perfect time to align on the naming convention for our images and we don't need to stick to any of the existing names...

Quoted 5 lines

Franklin,

Can you think of a unified naming for all the images, including base and full tisdk, as well as less common console and test images, that is scalable enough. As I'm thinking going back to arago-base-image and arago-

tisdk-image vs.

Quoted 2 lines

simplifying it to tisdk-base-image and tisdk-full-image. Plus it has to work with your other packagegroup restructure proposal... :)

[Franklin]

How about the following:

tisdk-rootfs-base-image -> arago-full-image ( me new proposed image)

tisdk-rootfs-image -> arago-full-sdk-image arago-base-tisdk-image -> arago- base-sdk-image arago-core-tisdk-image -> arago-core-sdk-image Tisdk-server- rootfs-image -> arago-server-sdk-image

Quoted 7 lines
Quoted 6 lines

Since our images are in meta-arago-distro which is dependent on meta-ti I think we could drop the "ti" from the image name to make it simpler. Based on the above logic I would probably change our packagegroups from using tisdk and simply call it sdk.
But if anyone has an issue I am ok with keeping tisdk in the packagegroups and images name.

[Franklin] Thoughts?

Yes, sorry, need bit more time...

#19 lore raw
In reply to Franklin S. Cooper Jr

You will need to update the setup script as well right? Because I think this would also match the expression used to find the rootfs used for the NFS setup

Quoted 49 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 17, 2013 3:13 PM
To: [email protected]
Cc: Cooper Jr., Franklin
Subject: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

* People are frequently confused by the difference in naming between the minimal
file system and the larger file system.
* Rename the minimal file system to mimic the naming convention of the larger
file system.

---
...e-tisdk-image.bb => tisdk-rootfs-base-image.bb} | 2 +-

1 files changed, 1 insertions(+), 1 deletions(-)

rename meta-arago-distro/recipes-core/images/{arago-base-tisdk- image.bb => tisdk-rootfs-base-image.bb} (87%)

(quoted diff) +0 -0

tisdk-image.bb b/meta-arago-distro/recipes-core/images/tisdk- rootfs-base-image.bb
similarity index 87%
rename from meta-arago-distro/recipes-core/images/arago-base- tisdk-image.bb
rename to meta-arago-distro/recipes-core/images/tisdk-rootfs-base- image.bb
index 2c0e217..a3a9123 100644
--- a/meta-arago-distro/recipes-core/images/arago-base-tisdk- image.bb
+++ b/meta-arago-distro/recipes-core/images/tisdk-rootfs-base- image.bb

meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb +1 -2
@@ -12,4 +12,4 @@ IMAGE_INSTALL += "\
    packagegroup-arago-base-tisdk \
    "
 
-export IMAGE_BASENAME = "arago-base-tisdk-image"
+export IMAGE_BASENAME = "tisdk-rootfs-base-image"
--

1.7.0.4

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

#20 lore raw

Yep. There will be some changes that need to be made to various SDK and back end scripts

Quoted 51 lines · Chase

You will need to update the setup script as well right? Because I think this would also match the expression used to find the rootfs used for the NFS setup

Quoted 49 lines

-----Original Message-----
From: [email protected] [mailto:meta-arago- [email protected]] On Behalf Of Cooper Jr., Franklin
Sent: Tuesday, September 17, 2013 3:13 PM
To: [email protected]
Cc: Cooper Jr., Franklin
Subject: [meta-arago] [PATCH 1/2] tisdk-rootfs-base-image: Rename base file system image

* People are frequently confused by the difference in naming between the minimal
file system and the larger file system.
* Rename the minimal file system to mimic the naming convention of the larger
file system.

---
...e-tisdk-image.bb => tisdk-rootfs-base-image.bb} | 2 +-

1 files changed, 1 insertions(+), 1 deletions(-)

rename meta-arago-distro/recipes-core/images/{arago-base-tisdk- image.bb => tisdk-rootfs-base-image.bb} (87%)

(quoted diff) +0 -0

tisdk-image.bb b/meta-arago-distro/recipes-core/images/tisdk- rootfs-base-image.bb
similarity index 87%
rename from meta-arago-distro/recipes-core/images/arago-base- tisdk-image.bb
rename to meta-arago-distro/recipes-core/images/tisdk-rootfs-base- image.bb
index 2c0e217..a3a9123 100644
--- a/meta-arago-distro/recipes-core/images/arago-base-tisdk- image.bb
+++ b/meta-arago-distro/recipes-core/images/tisdk-rootfs-base- image.bb

meta-arago-distro/recipes-core/images/tisdk-rootfs-base-image.bb renamed from meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb +1 -2
@@ -12,4 +12,4 @@ IMAGE_INSTALL += "\
   packagegroup-arago-base-tisdk \
   "
 
-export IMAGE_BASENAME = "arago-base-tisdk-image"
+export IMAGE_BASENAME = "tisdk-rootfs-base-image"
--

1.7.0.4

_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago