As I've been reading this thread I noticed one common theme. control.
The main problem that I think is holding us back is that some people
don't want to give up their control over *their* udev rules.
Yes, The packages are almost identical.
Yes, It would be easy to use cat to create extra rules specific to
different architectures in clfs.
Yes, Udev is a fast moving target.
These are all reason to create a common udev package. Instead of having
3 people working on the lfs udev package and 5 people working on the
clfs udev package. There could be 8 people working on the common udev
package and keeping that up to date and tested. It *could* exist in the
lfs repo but if it is not *just* lfs specific. Wouldn't it make more
sense to keep it in a seperate repo?
As Archaic just wrote in a recent email:
> But what about all the other changes? We need to discuss all differences
> and sort out which way to go every step
I think it would make a lot more sense to keep everything related to
udev in one place. The people that are given commit privileges wouldn't
be restricted to just the people in {c,h,}lfs but, rather to the people
that would like to work on the udev package.
The discussion of the udev package could happen on the lfs-dev list.
Maybe it would even have it's own mailing list and trac setup. As said
before, Udev is a fast moving target, 2 different packages trying to
achieve the exact same base (minus architecture specific rules) doesn't
make much sense.
As for ignoring the clfs package and using the lfs package, or
vice-versa. I don't think either one should be ignored but just
combined. The Makefile could be removed and replaced with cp commands to
copy the desired rules.
As I said in a previous email yesterday and in this email, there is
nothing wrong with either set of rules, There is only the existance of 2
different packages maintained by 2 different sets of people, where there
is no need for it. Both the people that worked on the lfs udev package
and the people that worked on the clfs udev package have seem to have a
solid understanding of writing udev rules. Lets put all those people
together.
I think a svn repo should be added for a common set of udev rules. I
will be willing to go through both the lfs rules and the clfs rules,
find all of the common rules, and mosh them together into one common
package. I don't think I will beable to get to it until the end of the
week, but by then, I hope there is a more solid decision.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
