Re: [yocto] Package relation between package.manifest and license.manifest

2016-10-31 Thread Khem Raj 

> On Oct 31, 2016, at 12:54 AM, Hugo Heutinck  wrote:
> 
> I am using the Jethro branch, which one are you using ?

morty/master

> 
> For me this provides quite a list of delta's, some seem to be related (e.g. 
> the dbus, dbus-glib, dbus-lib vs. dbus-1),
> but others are not (e.g. expat).
> 
> Was something on license file generation improved between Jethro and more 
> recent branches  ?
> 
> --- /tmp/a.manifest
> +++ /tmp/package.manifest
> @@ -24,9 +24,7 @@
>  cracklib
>  cronie
>  curl
> -dbus
> -dbus-glib
> -dbus-lib
> +dbus-1
>  debianutils
>  debianutils-run-parts
>  diffutils
> @@ -39,26 +37,16 @@
>  ed
>  elfutils
>  ethtool
> -expat
>  factory-tools
>  file
>  findutils
>  firmware-update
>  flex
> -freetype
>  fuser
>  gawk
> -gdbm
> -gdbm-compat
> -glib-2.0
> -glib-2.0-locale-en-gb
> -glibc
>  glibc-binary-localedata-en-gb
>  glibc-binary-localedata-en-us
>  glibc-locale-en-gb
> -gmp
> -gnutls
> -gnutls-openssl
>  grep
>  gzip
>  i2c-tools
> @@ -75,46 +63,70 @@
>  iputils-tracepath
>  iputils-tracepath6
>  iputils-traceroute6
> -json-c
>  kernel-crc-env
>  killall
>  kmod
>  led-control
>  less
> -libacl
> -libattr
> -libbz2
> -libcap
> -libcomerr
> -libcrypto
> -libcurl
> -libdw
> -libe2p
> -libelf
> -libestr
> +libacl1
> +libattr1
> +libblkid1
> +libbz2-0
> +libc6
> +libcap2
> +libcom-err2
> +libcrypto1.0.0
> +libcurl4
> +libdbus-1-3
> +libdbus-glib-1-2
> +libdw1
> +libe2p2
> +libelf1
> +libestr0
>  libevent
> -libext2fs
> -libffi
> -libgcc
> +libexpat1
> +libext2fs2
> +libfdisk1
> +libffi6
> +libfreetype6
> +libgcc1
>  libgcrypt
> -libgpg-error
> -libkmod
> +libgdbm-compat4
> +libgdbm4
> +libglib-2.0-0
> +libglib-2.0-locale-en-gb
> +libgmp10
> +libgnutls-openssl27
> +libgnutls28
> +libgpg-error0
> +libjson-c2
> +libkmod2
>  liblogging
> -liblzma
> -libpci
> -libpcre
> -libpython2
> -libss
> -libssl
> -libstdc++
> -libsysfs
> -libsystemd
> -libudev
> -libwrap
> -libx11
> -libxau
> -libxcb
> -libxdmcp
> +liblzma5
> +libmount1
> +libncurses5
> +libncursesw5
> +libpci3
> +libpcre1
> +libperl5
> +libpopt0
> +libpython2.7-1.0
> +libreadline6
> +libsmartcols1
> +libss2
> +libssl1.0.0
> +libstdc++6
> +libsysfs2
> +libsystemd0
> +libtinfo5
> +libudev1
> +libuuid1
> +libwrap0
> +libx11-6
> +libxau6
> +libxcb1
> +libxdmcp6
> +libz1
>  locale-base-en-gb
>  locale-base-en-us
>  logrotate
> @@ -130,9 +142,6 @@
>  mktemp
>  modutils-initscripts
>  ncurses
> -ncurses-libncurses
> -ncurses-libncursesw
> -ncurses-libtinfo
>  ncurses-terminfo
>  ncurses-terminfo-base
>  net-tools
> @@ -167,8 +176,6 @@
>  pciutils
>  pciutils-ids
>  perl
> -perl-lib
> -popt
>  procps
>  psmisc
>  psplash
> @@ -208,7 +215,6 @@
>  python-unittest
>  python-xml
>  python-xmlrpc
> -readline
>  rsyslog
>  run-postinsts
>  sed
> @@ -232,11 +238,6 @@
>  util-linux
>  util-linux-cfdisk
>  util-linux-fdisk
> -util-linux-libblkid
> -util-linux-libfdisk
> -util-linux-libmount
> -util-linux-libsmartcols
> -util-linux-libuuid
>  util-linux-losetup
>  util-linux-mkfs
>  util-linux-mount
> 
> 
> 2016-10-28 4:25 GMT+02:00 Khem Raj  >:
> 
>> On Oct 26, 2016, at 5:45 AM, Hugo Heutinck > > wrote:
>> 
>> Question: What is the relation between the package.manifest and 
>> license.manifest ?
>> 
>> After a yocto poky based image has been built there are 2 files in the 
>> licenses directory "tmp/deploy/licenses/image_name-datestamp"
>> 
>> One is the package.manifest, which if understood correctly is a list of all 
>> packages included in the image.
>> 
>> The second file is the license.manifest, but this one contains besides the 
>> package name also the version, recipe name and license of the package.
>> 
>> However if I compare the package names in both lists, there seem to be a  
>> number of packages in the license.manifest that are not part of the 
>> package.manifest. E.g. "readline, popt, expat, freetype".
>> 
>> Is the license.manifest a list of all items in the package.manifest + ?build 
>> dependencies? or something ?
> 
> They should be same.
> 
> try something like this
> cat license.manifest | grep "PACKAGE NAME: " | sed "s/PACKAGE NAME: //“ > 
> a.manifest
> diff a.manifest package.manifest
> 
> For me both files comes out same.
> 
> 
>> 
>> Regards,
>> 
>> H.Heutinck
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org 
>> https://lists.yoctoproject.org/listinfo/yocto 
>> 
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Package relation between package.manifest and license.manifest

2016-10-31 Thread Hugo Heutinck 
I am using the Jethro branch, which one are you using ?

For me this provides quite a list of delta's, some seem to be related (e.g.
the dbus, dbus-glib, dbus-lib vs. dbus-1),
but others are not (e.g. expat).

Was something on license file generation improved between Jethro and more
recent branches  ?

--- /tmp/a.manifest
+++ /tmp/package.manifest
@@ -24,9 +24,7 @@
 cracklib
 cronie
 curl
-dbus
-dbus-glib
-dbus-lib
+dbus-1
 debianutils
 debianutils-run-parts
 diffutils
@@ -39,26 +37,16 @@
 ed
 elfutils
 ethtool
-expat
 factory-tools
 file
 findutils
 firmware-update
 flex
-freetype
 fuser
 gawk
-gdbm
-gdbm-compat
-glib-2.0
-glib-2.0-locale-en-gb
-glibc
 glibc-binary-localedata-en-gb
 glibc-binary-localedata-en-us
 glibc-locale-en-gb
-gmp
-gnutls
-gnutls-openssl
 grep
 gzip
 i2c-tools
@@ -75,46 +63,70 @@
 iputils-tracepath
 iputils-tracepath6
 iputils-traceroute6
-json-c
 kernel-crc-env
 killall
 kmod
 led-control
 less
-libacl
-libattr
-libbz2
-libcap
-libcomerr
-libcrypto
-libcurl
-libdw
-libe2p
-libelf
-libestr
+libacl1
+libattr1
+libblkid1
+libbz2-0
+libc6
+libcap2
+libcom-err2
+libcrypto1.0.0
+libcurl4
+libdbus-1-3
+libdbus-glib-1-2
+libdw1
+libe2p2
+libelf1
+libestr0
 libevent
-libext2fs
-libffi
-libgcc
+libexpat1
+libext2fs2
+libfdisk1
+libffi6
+libfreetype6
+libgcc1
 libgcrypt
-libgpg-error
-libkmod
+libgdbm-compat4
+libgdbm4
+libglib-2.0-0
+libglib-2.0-locale-en-gb
+libgmp10
+libgnutls-openssl27
+libgnutls28
+libgpg-error0
+libjson-c2
+libkmod2
 liblogging
-liblzma
-libpci
-libpcre
-libpython2
-libss
-libssl
-libstdc++
-libsysfs
-libsystemd
-libudev
-libwrap
-libx11
-libxau
-libxcb
-libxdmcp
+liblzma5
+libmount1
+libncurses5
+libncursesw5
+libpci3
+libpcre1
+libperl5
+libpopt0
+libpython2.7-1.0
+libreadline6
+libsmartcols1
+libss2
+libssl1.0.0
+libstdc++6
+libsysfs2
+libsystemd0
+libtinfo5
+libudev1
+libuuid1
+libwrap0
+libx11-6
+libxau6
+libxcb1
+libxdmcp6
+libz1
 locale-base-en-gb
 locale-base-en-us
 logrotate
@@ -130,9 +142,6 @@
 mktemp
 modutils-initscripts
 ncurses
-ncurses-libncurses
-ncurses-libncursesw
-ncurses-libtinfo
 ncurses-terminfo
 ncurses-terminfo-base
 net-tools
@@ -167,8 +176,6 @@
 pciutils
 pciutils-ids
 perl
-perl-lib
-popt
 procps
 psmisc
 psplash
@@ -208,7 +215,6 @@
 python-unittest
 python-xml
 python-xmlrpc
-readline
 rsyslog
 run-postinsts
 sed
@@ -232,11 +238,6 @@
 util-linux
 util-linux-cfdisk
 util-linux-fdisk
-util-linux-libblkid
-util-linux-libfdisk
-util-linux-libmount
-util-linux-libsmartcols
-util-linux-libuuid
 util-linux-losetup
 util-linux-mkfs
 util-linux-mount


2016-10-28 4:25 GMT+02:00 Khem Raj :

>
> On Oct 26, 2016, at 5:45 AM, Hugo Heutinck  wrote:
>
> Question: What is the relation between the package.manifest and
> license.manifest ?
>
> After a yocto poky based image has been built there are 2 files in the
> licenses directory "tmp/deploy/licenses/*image_name-datestamp*"
>
> One is the package.manifest, which if understood correctly is a list of
> all packages included in the image.
>
> The second file is the license.manifest, but this one contains besides the
> package name also the version, recipe name and license of the package.
>
> However if I compare the package names in both lists, there seem to be a
> number of packages in the license.manifest that are not part of the
> package.manifest. E.g. "readline, popt, expat, freetype".
>
> Is the license.manifest a list of all items in the package.manifest +
> ?build dependencies? or something ?
>
>
> They should be same.
>
> try something like this
> cat license.manifest | grep "PACKAGE NAME: " | sed "s/PACKAGE NAME: //“ >
> a.manifest
> diff a.manifest package.manifest
>
> For me both files comes out same.
>
>
>
> Regards,
>
> H.Heutinck
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Package relation between package.manifest and license.manifest

2016-10-27 Thread Khem Raj 

> On Oct 26, 2016, at 5:45 AM, Hugo Heutinck  wrote:
> 
> Question: What is the relation between the package.manifest and 
> license.manifest ?
> 
> After a yocto poky based image has been built there are 2 files in the 
> licenses directory "tmp/deploy/licenses/image_name-datestamp"
> 
> One is the package.manifest, which if understood correctly is a list of all 
> packages included in the image.
> 
> The second file is the license.manifest, but this one contains besides the 
> package name also the version, recipe name and license of the package.
> 
> However if I compare the package names in both lists, there seem to be a  
> number of packages in the license.manifest that are not part of the 
> package.manifest. E.g. "readline, popt, expat, freetype".
> 
> Is the license.manifest a list of all items in the package.manifest + ?build 
> dependencies? or something ?

They should be same.

try something like this
cat license.manifest | grep "PACKAGE NAME: " | sed "s/PACKAGE NAME: //“ > 
a.manifest
diff a.manifest package.manifest

For me both files comes out same.


> 
> Regards,
> 
> H.Heutinck
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Package relation between package.manifest and license.manifest

2016-10-26 Thread Hugo Heutinck 
Question: What is the relation between the package.manifest and
license.manifest ?

After a yocto poky based image has been built there are 2 files in the
licenses directory "tmp/deploy/licenses/*image_name-datestamp*"

One is the package.manifest, which if understood correctly is a list of all
packages included in the image.

The second file is the license.manifest, but this one contains besides the
package name also the version, recipe name and license of the package.

However if I compare the package names in both lists, there seem to be a
number of packages in the license.manifest that are not part of the
package.manifest. E.g. "readline, popt, expat, freetype".

Is the license.manifest a list of all items in the package.manifest +
?build dependencies? or something ?

Regards,

H.Heutinck
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto