These recipes are used to build release images for the BeagleBoard community using the sdcard_image class in meta-ti
Signed-off-by: Joel A Fernandes <joelagnel@ti.com>
These recipes are used to build release images for the BeagleBoard community using the sdcard_image class in meta-ti
Signed-off-by: Joel A Fernandes <joelagnel@ti.com>
Please apply this patch to "meta-angstrom", thanks.
Please apply this patch to "meta-angstrom", thanks.
These would seem better in meta-ti, no?
Probably, but then again it is derived from "systemd-gnome-image" from
Angstrom and has a bunch of angstrom-tasks.
Thanks,
Joel
Please apply this patch to "meta-angstrom", thanks.
These would seem better in meta-ti, no?
Probably, but then again it is derived from "systemd-gnome-image" from
Angstrom and has a bunch of angstrom-tasks.
Perhaps it doesn't belong in meta-angstrom if it is target-specific.
Perhaps it doesn't belong in meta-ti if it is distro-specific.
It would make sense to go into a repository with a motivated owner.
git.beagleboard.org never came to life because gitorious is too hard
to configure.
Would it make sense to have a meta-beagleboard that depends on
Angstrom in the meta-ti repository, but not the meta-ti layer?