[haiku-development] Re: freebsd vendor branch directory structure
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 21 Aug 2009 21:09:54 +0200 CEST
Hi Michael,
Michael Weirauch <dev@xxxxxxxxxxx> wrote:
> I am currently trying to help Oliver (R.D.) find the right place for
> the
> FreeBSD libsdp in the vendor branch from their 7.2.0 release.
>
> From my understanding of the vendor branch and it's use, the current
> structure seems to have some issues/leaves questions: [1]
>
> * the "current" and RELENG* actually host the contents of the sys-
> directory
> in their root instead of RELENG*/sys/dev/ for example
> (Yes, I asked julun before to replicate this when importing the
> e1000 driver
> and kinda supported this issue.)
Actually, since we only import smaller components, and obviously not
all of them at the same time, I guess we should let the components come
first, and put the current/release stuff below them.
This way, one would always know the correct version.
Only updating all drivers would be more work this way.
> clear from which version of FreeBSD the code stems from. Or is this
> a
> non-issue of having version-mixed-up code in the vendor/current?
It's definitely confusing.
> * (minor) FreeBSD switched core dev to their svn SCM IIRC and the tag
> for the
> releases lives in /releases/x.x.x/ [2]
> Is it desired to replicate this structure for any new imports.
> (e.g. vendor/freebsd/releases/7.2.0/...)
I would just name the tag 7.2.0, then, no need for another directory
level.
Bye,
Axel.
Other related posts:
