[Buildroot] Buildroot Developer Day, Friday 3rd February, Brussels
Peter Korsgaard
jacmet at uclibc.org
Mon Jan 30 15:09:30 UTC 2012
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin+buildroot at gmail.com> writes:
Hi,
>> I've maintained buildroot support for a number of projects at $WORK for
>> 5+ years, and the way I've always handled this is with
>> branches/tags. Buildroot head moves forward and follows upstream, but
>> projects might decide to freeze (or if needed branch) once they have a
>> stable setup. I use the same approach with the Linux kernel and u-boot,
>> without any real problems.
Thomas> Essentially this is the same as creating two independent buildroot
Thomas> repositories, one for each project. This approach does not have a
Thomas> single mainstream that allows different configurations for each
Thomas> project, but rather creates two streams, each with their own
Thomas> configuration. In my case, since we have many similar but different
Thomas> products, I'd prefer to be able to keep one stream.
Here as well. That stream is the head branch. Branching only happens
once a project no longer wants to follow the main development. This
doesn't mean that the project gets removed from the head version, just
that it is no longer used to cut releases from.
>> I would prefer to not add too much complexity for such a specialized /
>> advanced feature.
Thomas> In its basic form, I don't think it has to be very complex. Although I
Thomas> haven't looked into this in detail, it could be enough to allow to
Thomas> override FOO_VERSION from the configuration or from a certain
Thomas> project-specific file.
What about other version dependencies? Patches, different dependencies,
configure options, ..?
>> yes, I think this is good to go, it just needs to be implemented. With
>> us being this close to 2012.02-rc1 I might wait until I start the next
>> branch though.
Thomas> I understand. I haven't had a lot of time lately either to submit patches.
No problem. I'll do it myself if you don't get around to do it.
--
Bye, Peter Korsgaard
More information about the buildroot
mailing list