Am Thu, 6 Jul 2017 01:09:38 +0200 hat aTc atc@k-n-p.org geschrieben:
Hi,
aTc, now that you have more experience with building the Debian stuff, maybe you could let me know here how many gits and what gits we need.
I already created a public packages group on dev.pyra-handhelds.com , and pushing my git stuff to it (slowly, have to check everything and do a few cleanups in places). I currently build/maintain them with gbp
Notice: As mentioned in one of the mails, I've currently switched to GitLab on dev.pyra-handhelds.com, so it's empty right now, as I need to know which projects and subprojects I need to create.
So we should restart the GITs there from scratch, in my opinion.
Do you have everything you need or should I switch back to Indefero for the moment?
You should register at dev.pyra-handhelds.com, then I can add you to the group and you can create and manage all the needed gits yourself.
It seems like image creation should largely just build the image out of Debian packages that are included in a "staging" apt repository, rather than recompiling everything every time you build an image.
Yes, Openembedded was more designed so that you had everything in a single tree you had complete control over, with packages you all built yourself. With Debian you just have packages that some package maintainer puts on a repo, and you grab the latest versions to assemble your image.
Okay. So we simply update the debian packages once we updated them and the image creation tool should automatically pull in the new packages as well. Understood.
With three different repositories, you could trigger different image builds that are targeted at automated builds with the latest untested stuff, development builds that have been somewhat tested, and builds targeted at the end-user.
I could do with some help setting up the repo that way. I've currently got just a basic single stable repo reprepro setup where i can dput a package to, and then manually run processincomming to get everything online.
Yes, it would be nice to have unstable, testing and stable (or at least unstable and testing/stable, so users can also test last-minute patches).