rename packages/ to recipes/ per earlier agreement
Subsystems (9)
PATCH 2/3 recipes: fix hardcoded instances of packages/
In reply to Denys Dmytriyenko--- recipes/kexecboot/linux-kexecboot.inc | 2 +- recipes/libffi/libffi_2.0+gcc4.3.2.bb | 2 +- recipes/libffi/libffi_3.0.8.bb | 2 +- recipes/mamona/gcc-noemu_4.1.1.bb | 2 +- recipes/mamona/gcc-noemu_4.1.2.bb | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-)
recipes/kexecboot/linux-kexecboot.inc +1 -1
@@ -6,7 +6,7 @@ SRC_URI = "file://defconfig" LOGO_SIZE = '${@base_conditional("GUI_MACHINE_CLASS", "bigscreen", "vga", "qvga", d)}' SRC_URI += "file://${LOGO_SIZE}/logo_linux_clut224.ppm.bz2" -require packages/linux/linux.inc +require recipes/linux/linux.inc DONT_CHECK_KERNELSIZE = "" INITRAMFS_IMAGE = "initramfs-kexecboot-image"
recipes/libffi/libffi_2.0+gcc4.3.2.bb +1 -1
@@ -1,4 +1,4 @@ -require packages/gcc/gcc-common.inc +require recipes/gcc/gcc-common.inc SECTION = "libs" DESCRIPTION = "Foreign Function Interface library" LICENSE = "libffi"
recipes/libffi/libffi_3.0.8.bb +1 -1
@@ -1,4 +1,4 @@ -require packages/gcc/gcc-common.inc +require recipes/gcc/gcc-common.inc SECTION = "libs" DESCRIPTION = "Foreign Function Interface library"
recipes/mamona/gcc-noemu_4.1.1.bb +1 -1
@@ -57,7 +57,7 @@ JAVA_arm = "" JAVA = "" LANGUAGES = "c,c++${FORTRAN}${JAVA}" -require packages/gcc/gcc-${PV}.inc +require recipes/gcc/gcc-${PV}.inc EXTRA_OECONF += "--disable-libspp --with-slibdir=\"/lib\""
recipes/mamona/gcc-noemu_4.1.2.bb +1 -1
@@ -77,7 +77,7 @@ JAVA_arm = "" LANGUAGES = "c,c++${FORTRAN}${JAVA}" -require packages/gcc/gcc-${PV}.inc +require recipes/gcc/gcc-${PV}.inc EXTRA_OECONF += " --disable-libssp --with-slibdir=\"/lib\" "
Signature · 1 line
1.6.0.6
Re: [PATCH 2/3] recipes: fix hardcoded instances of packages/
Quoted 60 lines · On Monday 16 March 2009 16:32:43 Denys Dmytriyenko wrote:
Signed-off-by Denys Dmytriyenko <[email protected]>--- recipes/kexecboot/linux-kexecboot.inc | 2 +- recipes/libffi/libffi_2.0+gcc4.3.2.bb | 2 +- recipes/libffi/libffi_3.0.8.bb | 2 +- recipes/mamona/gcc-noemu_4.1.1.bb | 2 +- recipes/mamona/gcc-noemu_4.1.2.bb | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-)recipes/kexecboot/linux-kexecboot.inc +1
-1@@ -6,7 +6,7 @@ SRC_URI = "file://defconfig" LOGO_SIZE = '${@base_conditional("GUI_MACHINE_CLASS", "bigscreen", "vga", "qvga", d)}' SRC_URI += "file://${LOGO_SIZE}/logo_linux_clut224.ppm.bz2" -require packages/linux/linux.inc +require recipes/linux/linux.inc DONT_CHECK_KERNELSIZE = "" INITRAMFS_IMAGE = "initramfs-kexecboot-image"recipes/libffi/libffi_2.0+gcc4.3.2.bb +1
-1@@ -1,4 +1,4 @@ -require packages/gcc/gcc-common.inc +require recipes/gcc/gcc-common.inc SECTION = "libs" DESCRIPTION = "Foreign Function Interface library" LICENSE = "libffi"recipes/libffi/libffi_3.0.8.bb +1
-1@@ -1,4 +1,4 @@ -require packages/gcc/gcc-common.inc +require recipes/gcc/gcc-common.inc SECTION = "libs" DESCRIPTION = "Foreign Function Interface library"recipes/mamona/gcc-noemu_4.1.1.bb +1
-1@@ -57,7 +57,7 @@ JAVA_arm = "" JAVA = "" LANGUAGES = "c,c++${FORTRAN}${JAVA}" -require packages/gcc/gcc-${PV}.inc +require recipes/gcc/gcc-${PV}.inc EXTRA_OECONF += "--disable-libspp --with-slibdir=\"/lib\""recipes/mamona/gcc-noemu_4.1.2.bb +0
-0
recipes/mamona/gcc-noemu_4.1.2.bb JAVA_arm = "" · line 83
Quoted 8 lines
recipes/mamona/gcc-noemu_4.1.2.bb +1
-1@@ -77,7 +77,7 @@ JAVA_arm = "" LANGUAGES = "c,c++${FORTRAN}${JAVA}" -require packages/gcc/gcc-${PV}.inc +require recipes/gcc/gcc-${PV}.inc EXTRA_OECONF += " --disable-libssp --with-slibdir=\"/lib\" "
Ack. A small nit you also need to make necessary changes in conf files I guess local.conf.sample etc will need to be changed.
Signature · 1 line
Khem Raj
PATCH 3/3 base.bbclass: fix base_get_scmbasepath() to look for recipes/ and fall back to packages/ while parsing BBFILES
In reply to Denys Dmytriyenko--- classes/base.bbclass | 8 +++++++- 1 files changed, 7 insertions(+), 1 deletions(-)
classes/base.bbclass +7 -1
@@ -773,7 +773,13 @@ python base_do_unpack() { def base_get_scmbasepath(d): import bb path_to_bbfiles = bb.data.getVar( 'BBFILES', d, 1 ).split() - return path_to_bbfiles[0][:path_to_bbfiles[0].rindex( "packages" )] + + try: + index = path_to_bbfiles[0].rindex( "recipes" ) + except ValueError: + index = path_to_bbfiles[0].rindex( "packages" ) + + return path_to_bbfiles[0][:index] def base_get_metadata_monotone_branch(d): monotone_branch = "<unknown>"
Signature · 1 line
1.6.0.6
Re: [PATCH 3/3] base.bbclass: fix base_get_scmbasepath() to look for recipes/ and fall back to packages/ while parsing BBFILES
Denys Dmytriyenko <[email protected]> writes:
[...]
Quoted 7 lines
classes/base.bbclass +0
-1@@ -773,7 +773,13 @@ python base_do_unpack() { def base_get_scmbasepath(d): import bb path_to_bbfiles = bb.data.getVar( 'BBFILES', d, 1 ).split() - return path_to_bbfiles[0][:path_to_bbfiles[0].rindex( "packages" )]
classes/base.bbclass python base_do_unpack() { · line 785
Quoted 10 lines
classes/base.bbclass +7
-0+ + try: + index = path_to_bbfiles[0].rindex( "recipes" ) + except ValueError: + index = path_to_bbfiles[0].rindex( "packages" ) + + return path_to_bbfiles[0][:index] def base_get_metadata_monotone_branch(d): monotone_branch = "<unknown>"
In my opinion, while it makes life easier the result of it is mixed environments.
I'm still using packages/ in our local distro and I haven't yet found the time to merge current tree since we've a lot of local recipes that will break and this change could make it simple but I still refrain about having it included.
It looks like the logical thing is kind of "force" people to handle it.
My 2c.
Signature · 3 lines
Otavio Salvador O.S. Systems E-mail: [email protected] http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
Re: [PATCH 3/3] base.bbclass: fix base_get_scmbasepath() to look for recipes/ and fall back to packages/ while parsing BBFILES
Quoted 26 lines · Otavio Salvador
Denys Dmytriyenko <[email protected]> writes:
[...]
Quoted 7 lines
classes/base.bbclass +0
-1@@ -773,7 +773,13 @@ python base_do_unpack() { def base_get_scmbasepath(d): import bb path_to_bbfiles = bb.data.getVar( 'BBFILES', d, 1 ).split() - return path_to_bbfiles[0][:path_to_bbfiles[0].rindex( "packages" )]classes/base.bbclass python base_do_unpack() { · line 785
Quoted 10 lines
classes/base.bbclass +7
-0+ + try: + index = path_to_bbfiles[0].rindex( "recipes" ) + except ValueError: + index = path_to_bbfiles[0].rindex( "packages" ) + + return path_to_bbfiles[0][:index] def base_get_metadata_monotone_branch(d): monotone_branch = "<unknown>"In my opinion, while it makes life easier the result of it is mixed environments.
Quoted 6 lines
I'm still using packages/ in our local distro and I haven't yet found the time to merge current tree since we've a lot of local recipes that will break and this change could make it simple but I still refrain about having it included.
It looks like the logical thing is kind of "force" people to handle it.
First you said you are not ready to make the switch, and then you are saying we need to force people into it... :)
Anyway, it doesn't matter anymore, as this code has been replaced completely by one of kergoth's recent commits.
Signature · 1 line
Denys
Re: [PATCH 3/3] base.bbclass: fix base_get_scmbasepath() to look for recipes/ and fall back to packages/ while parsing BBFILES
Quoted 10 lines · Denys Dmytriyenko
Quoted 9 lines · Otavio Salvador
Denys Dmytriyenko <[email protected]> writes:
In my opinion, while it makes life easier the result of it is mixed environments.I'm still using packages/ in our local distro and I haven't yet found the time to merge current tree since we've a lot of local recipes that will break and this change could make it simple but I still refrain about having it included.
Quoted 4 lines
Quoted 1 line
It looks like the logical thing is kind of "force" people to handle it.
First you said you are not ready to make the switch, and then you are saying we need to force people into it... :)
Well me not being ready to make the switch is due our deadlines. This doesn't change my general idea about forcing people to handle it and avoid those "backward compatibility hacks" to stay forever ;-)
Quoted 2 lines
Anyway, it doesn't matter anymore, as this code has been replaced completely by one of kergoth's recent commits.
Oh! I didn't see it. Please archive it in PatchWork then :-D
Signature · 3 lines
Otavio Salvador O.S. Systems E-mail: [email protected] http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
Re: [PATCH 3/3] base.bbclass: fix base_get_scmbasepath() to look for recipes/ and fall back to packages/ while parsing BBFILES
Quoted 15 lines · Otavio Salvador
Quoted 5 lines · Denys Dmytriyenko
Quoted 4 lines · Otavio Salvador
Denys Dmytriyenko <[email protected]> writes:
In my opinion, while it makes life easier the result of it is mixed environments.Quoted 8 lines
Quoted 6 lines
I'm still using packages/ in our local distro and I haven't yet found the time to merge current tree since we've a lot of local recipes that will break and this change could make it simple but I still refrain about having it included.
It looks like the logical thing is kind of "force" people to handle it.
First you said you are not ready to make the switch, and then you are saying we need to force people into it... :)
Quoted 8 lines
Well me not being ready to make the switch is due our deadlines. This doesn't change my general idea about forcing people to handle it and avoid those "backward compatibility hacks" to stay forever ;-)
Quoted 2 lines
Anyway, it doesn't matter anymore, as this code has been replaced completely by one of kergoth's recent commits.
Oh! I didn't see it. Please archive it in PatchWork then :-D
You should be able to change the flag yourself. When people create accounts on Patchwork, I set them to allow them to change patch states.
Philip
PATCH 3/3 base.bbclass: fix base_get_scmbasepath() to look for recipes/ and fall back to packages/ while parsing BBFILES
In reply to Denys DmytriyenkoQuoted 4 lines · Denys Dmytriyenko
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Ack. But can you please tag the revision immediately preceeding the
commit of this change so we have some easy-to-reference point[*] in the history?
- Mike
[*] In accordance with the laws of Murphy, doing this will ensure that nobody will ever actually have to use this easy-to-reference point.
Quoted 6 lines · Mike (mwester)
Quoted 4 lines · Denys Dmytriyenko
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Quoted 8 lines
Ack. But can you please tag the revision immediately preceeding the
commit of this change so we have some easy-to-reference point[*] in the history?- Mike
[*] In accordance with the laws of Murphy, doing this will ensure that nobody will ever actually have to use this easy-to-reference point.
+1, same logic.
Philip
Quoted 10 lines · Mike (mwester)
Quoted 4 lines · Denys Dmytriyenko
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Ack. But can you please tag the revision immediately preceeding the
commit of this change so we have some easy-to-reference point[*] in the history?
Done. mv-packages-to-recipes-pre and mv-packages-to-recipes-post are the tags applied right before and right after the change.
Quoted 2 lines
[*] In accordance with the laws of Murphy, doing this will ensure that nobody will ever actually have to use this easy-to-reference point.
Good point! Let's hope.
Signature · 1 line
Denys
Quoted 8 lines · Denys Dmytriyenko
Quoted 7 lines · Mike (mwester)
Quoted 4 lines · Denys Dmytriyenko
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Quoted 7 lines
Quoted 3 lines
Ack. But can you please tag the revision immediately preceeding the commit of this change so we have some easy-to-reference point[*] in the history?
Done. mv-packages-to-recipes-pre and mv-packages-to-recipes-post are the tags applied right before and right after the change.
Is the packages directory supposed to be empty now? There are still a few subdirs left:
roth@dorkboy:~/dev/OE/openembedded/packages$ ls -1 automake/ blueprobe/ busybox/ coreutils/ gnome/ gpe-gallery/ pkgconfig/ pyneo/ qt4/ udev/
I will generate a patch to the usermanual to note the new recipes directory. I am curious is the old packages will still be kept around or if it will be completely removed. If kept, how would it be described versus the recipes dir?
Ted Roth
Quoted 21 lines · Theodore A. Roth
Quoted 8 lines · Denys Dmytriyenko
Quoted 7 lines · Mike (mwester)
Quoted 4 lines · Denys Dmytriyenko
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Quoted 7 lines
Quoted 3 lines
Ack. But can you please tag the revision immediately preceeding the commit of this change so we have some easy-to-reference point[*] in the history?
Done. mv-packages-to-recipes-pre and mv-packages-to-recipes-post are the tags applied right before and right after the change.
Is the packages directory supposed to be empty now? There are still a few subdirs left:
Quoted 11 lines
roth@dorkboy:~/dev/OE/openembedded/packages$ ls -1 automake/ blueprobe/ busybox/ coreutils/ gnome/ gpe-gallery/ pkgconfig/ pyneo/ qt4/ udev/
Those are empty directories (unless you have uncommited changes in them). That is because git only keeps track of files, not directories. A simple rename of a single directory resulted in thousands of renames of individual files. When you did "git pull" all the files were moved, leaving the old hierarchy empty. It should be safe to remove by "rm -r packages" - if there are still files there, rm will fail. And if you do a fresh "git clone", there will be no packages/ directory there.
Quoted 2 lines
I will generate a patch to the usermanual to note the new recipes directory.
Thanks for taking care of the documentation.
Quoted 3 lines
I am curious is the old packages will still be kept around or if it will be completely removed. If kept, how would it be described versus the recipes dir?
Now recipes/ directory name represents its contents. Packages are normally generated by running/processing recipes. But they are placed inside DEPLOY_DIR and I'm not sure there is any need in packages/ directory in the repository.
Signature · 1 line
Denys
Quoted 34 lines · Denys Dmytriyenko
Quoted 21 lines · Theodore A. Roth
Quoted 8 lines · Denys Dmytriyenko
Quoted 7 lines · Mike (mwester)
Quoted 4 lines · Denys Dmytriyenko
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Quoted 7 lines
Quoted 3 lines
Ack. But can you please tag the revision immediately preceeding the commit of this change so we have some easy-to-reference point[*] in the history?
Done. mv-packages-to-recipes-pre and mv-packages-to-recipes-post are the tags applied right before and right after the change.
Is the packages directory supposed to be empty now? There are still a few subdirs left:
Quoted 11 lines
roth@dorkboy:~/dev/OE/openembedded/packages$ ls -1 automake/ blueprobe/ busybox/ coreutils/ gnome/ gpe-gallery/ pkgconfig/ pyneo/ qt4/ udev/
Quoted 7 lines
Those are empty directories (unless you have uncommited changes in them). That is because git only keeps track of files, not directories. A simple rename of a single directory resulted in thousands of renames of individual files. When you did "git pull" all the files were moved, leaving the old hierarchy empty. It should be safe to remove by "rm -r packages" - if there are still files there, rm will fail. And if you do a fresh "git clone", there will be no packages/ directory there.
Argh, the above "rm -r packages" is not safe, as it won't fail removing files. Please use this command instead:
find packages -depth -type d -empty -exec rmdir {} \;
Quoted 12 lines
Quoted 2 lines
I will generate a patch to the usermanual to note the new recipes directory.
Thanks for taking care of the documentation.
Quoted 3 lines
I am curious is the old packages will still be kept around or if it will be completely removed. If kept, how would it be described versus the recipes dir?
Now recipes/ directory name represents its contents. Packages are normally generated by running/processing recipes. But they are placed inside
DEPLOY_DIRand I'm not sure there is any need in packages/ directory in the repository.
Signature · 1 line
Denys
There are still a few related tasks pending.
One of them is updating the wiki. (e.g.
http://wiki.openembedded.net/index.php/Getting_Started)
probably it is most convenient if someone does it who can access the system and the files and directly invoke an editor (assuming it are files and not in a database).
Frans.
2009/3/19 Denys Dmytriyenko <[email protected]>:
Quoted 69 lines · Denys Dmytriyenko
Quoted 34 lines · Theodore A. Roth
Quoted 21 lines · Denys Dmytriyenko
Quoted 8 lines · Mike (mwester)
Quoted 7 lines
Quoted 4 lines · Denys Dmytriyenko
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Quoted 7 lines
Quoted 3 lines
Ack. But can you please tag the revision immediately preceeding the commit of this change so we have some easy-to-reference point[*] in the history?
Done. mv-packages-to-recipes-pre and mv-packages-to-recipes-post are the tags applied right before and right after the change.
Is the packages directory supposed to be empty now? There are still a few subdirs left:
Quoted 11 lines
roth@dorkboy:~/dev/OE/openembedded/packages$ ls -1 automake/ blueprobe/ busybox/ coreutils/ gnome/ gpe-gallery/ pkgconfig/ pyneo/ qt4/ udev/Quoted 7 lines
Those are empty directories (unless you have uncommited changes in them). That is because git only keeps track of files, not directories. A simple rename of a single directory resulted in thousands of renames of individual files. When you did "git pull" all the files were moved, leaving the old hierarchy empty. It should be safe to remove by "rm -r packages" - if there are still files there, rm will fail. And if you do a fresh "git clone", there will be no packages/ directory there.
Argh, the above "rm -r packages" is not safe, as it won't fail removing files. Please use this command instead:
find packages -depth -type d -empty -exec rmdir {} \;Quoted 5 lines
Quoted 2 lines
I will generate a patch to the usermanual to note the new recipes directory.
Thanks for taking care of the documentation.
Quoted 7 lines
Quoted 3 lines
I am curious is the old packages will still be kept around or if it will be completely removed. If kept, how would it be described versus the recipes dir?
Now recipes/ directory name represents its contents. Packages are normally generated by running/processing recipes. But they are placed inside
DEPLOY_DIRand I'm not sure there is any need in packages/ directory in the repository.--
Denys_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Quoted 7 lines · Frans Meulenbroeks
There are still a few related tasks pending.
One of them is updating the wiki. (e.g.
http://wiki.openembedded.net/index.php/Getting_Started)
probably it is most convenient if someone does it who can access the system and the files and directly invoke an editor (assuming it are files and not in a database).
Instead of updating the wiki, why not just have the wiki have a link to the user manual at docs.openembedded.org? I have recently pulled most of the info about getting started from the wiki into the user manual.
Suppose that there is a stable branch that has different getting started instructions than the dev branch. That makes the wiki either be wrong in one case, or have to discuss both branches.
Ted Roth
Quoted 76 lines
2009/3/19 Denys Dmytriyenko <[email protected]>:
Quoted 60 lines · Denys Dmytriyenko
Quoted 34 lines · Theodore A. Roth
Quoted 21 lines · Denys Dmytriyenko
Quoted 8 lines · Mike (mwester)
Quoted 7 lines
Quoted 4 lines · Denys Dmytriyenko
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Quoted 7 lines
Quoted 3 lines
Ack. But can you please tag the revision immediately preceeding the commit of this change so we have some easy-to-reference point[*] in the history?
Done. mv-packages-to-recipes-pre and mv-packages-to-recipes-post are the tags applied right before and right after the change.
Is the packages directory supposed to be empty now? There are still a few subdirs left:
Quoted 11 lines
roth@dorkboy:~/dev/OE/openembedded/packages$ ls -1 automake/ blueprobe/ busybox/ coreutils/ gnome/ gpe-gallery/ pkgconfig/ pyneo/ qt4/ udev/Quoted 7 lines
Those are empty directories (unless you have uncommited changes in them). That is because git only keeps track of files, not directories. A simple rename of a single directory resulted in thousands of renames of individual files. When you did "git pull" all the files were moved, leaving the old hierarchy empty. It should be safe to remove by "rm -r packages" - if there are still files there, rm will fail. And if you do a fresh "git clone", there will be no packages/ directory there.
Argh, the above "rm -r packages" is not safe, as it won't fail removing files. Please use this command instead:
find packages -depth -type d -empty -exec rmdir {} \;Quoted 5 lines
Quoted 2 lines
I will generate a patch to the usermanual to note the new recipes directory.
Thanks for taking care of the documentation.
Quoted 7 lines
Quoted 3 lines
I am curious is the old packages will still be kept around or if it will be completely removed. If kept, how would it be described versus the recipes dir?
Now recipes/ directory name represents its contents. Packages are normally generated by running/processing recipes. But they are placed inside
DEPLOY_DIRand I'm not sure there is any need in packages/ directory in the repository.Quoted 9 lines
--
Denys_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Apparently I had some unpushed commits on packages. I was unaware of these and when pushing of course they created the files in packages, I've added a commit to move those to recipes and pushed that one. I hope this did not create a stale dir packages in the archive, or messed up in a different way...
Anyway, apologies for any inconvenience!
Frans.
Dnia wtorek, 17 marca 2009 o 00:32:41 Denys Dmytriyenko napisał(a):
Quoted 6 lines
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Quoted 7 lines
[1] http://thread.gmane.org/gmane.comp.handhelds.openembedded/21326
Denys Dmytriyenko (3):
rename packages/ to recipes/ per earlier agreement
recipes: fix hardcoded instances of packages/ base.bbclass: fixbase_get_scmbasepath()to look for recipes/ and
fall back to packages/ while parsing BBFILES
Regards,
Signature · 3 lines
JID: [email protected] Website: http://marcin.juszkiewicz.com.pl/ LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
Quoted 5 lines · Denys Dmytriyenko
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Quoted 7 lines
[1] http://thread.gmane.org/gmane.comp.handhelds.openembedded/21326
Denys Dmytriyenko (3):
rename packages/ to recipes/ per earlier agreement
recipes: fix hardcoded instances of packages/ base.bbclass: fixbase_get_scmbasepath()to look for recipes/ and
fall back to packages/ while parsing BBFILES
Now, if you use patchwork, these acks and SOBs get added to your patch automagically :)
regards,
Koen
Frans Meulenbroeks
Acked-by2009/3/17 Koen Kooi <[email protected]>:
Quoted 22 lines · Denys Dmytriyenko
Quoted 6 lines
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Quoted 7 lines
[1] http://thread.gmane.org/gmane.comp.handhelds.openembedded/21326
Denys Dmytriyenko (3):
rename packages/ to recipes/ per earlier agreement
recipes: fix hardcoded instances of packages/ base.bbclass: fixbase_get_scmbasepath()to look for recipes/ and fall back to packages/ while parsing BBFILESAcked-by Koen Kooi <[email protected]>Now, if you use patchwork, these acks and SOBs get added to your patch automagically :)
regards,
Quoted 8 lines
Koen
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
if someone is interested in my blessing :-) :-) :-)
Frans
Otavio Salvador
Acked-byQuoted 26 lines · Frans Meulenbroeks
2009/3/17 Koen Kooi <[email protected]>:
Quoted 25 lines · Denys Dmytriyenko
Quoted 6 lines
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Quoted 7 lines
[1] http://thread.gmane.org/gmane.comp.handhelds.openembedded/21326
Denys Dmytriyenko (3):
rename packages/ to recipes/ per earlier agreement
recipes: fix hardcoded instances of packages/ base.bbclass: fixbase_get_scmbasepath()to look for recipes/ and fall back to packages/ while parsing BBFILESAcked-by Koen Kooi <[email protected]>Now, if you use patchwork, these acks and SOBs get added to your patch automagically :)
regards,
Koen
Quoted 6 lines
Quoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Signature · 3 lines
Otavio Salvador O.S. Systems E-mail: [email protected] http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
Quoted 28 lines · Otavio Salvador
Quoted 26 lines · Frans Meulenbroeks
2009/3/17 Koen Kooi <[email protected]>:
Quoted 25 lines · Denys Dmytriyenko
Quoted 6 lines
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Quoted 7 lines
[1] http://thread.gmane.org/gmane.comp.handhelds.openembedded/21326
Denys Dmytriyenko (3):
rename packages/ to recipes/ per earlier agreement
recipes: fix hardcoded instances of packages/ base.bbclass: fixbase_get_scmbasepath()to look for recipes/ and fall back to packages/ while parsing BBFILESAcked-by Koen Kooi <[email protected]>Now, if you use patchwork, these acks and SOBs get added to your patch automagically :)
regards,
Koen
Quoted 8 lines
Quoted 6 lines
Quoted 5 lines
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-develAcked-by Otavio Salvador <[email protected]>
Sorry, already commited. Thanks anyway!
Signature · 1 line
Denys
Quoted 14 lines · Koen Kooi
Quoted 5 lines · Denys Dmytriyenko
Renaming packages/ directory to recipes/, as one of the several structural changes, was proposed by Koen[1] and agreed/approved by many. Since Koen currently doesn't have time/ability to do the change, and some people are too eager to wait any longer, he asked me to do it. Please ack/nack.
Quoted 7 lines
[1] http://thread.gmane.org/gmane.comp.handhelds.openembedded/21326
Denys Dmytriyenko (3):
rename packages/ to recipes/ per earlier agreement
recipes: fix hardcoded instances of packages/ base.bbclass: fixbase_get_scmbasepath()to look for recipes/ and
fall back to packages/ while parsing BBFILES
Quoted 4 lines
Acked-by Koen Kooi <[email protected]>Now, if you use patchwork, these acks and SOBs get added to your patch automagically :)
Cool! I guess I need to take a look at it some time...
Signature · 1 line
Denys