Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Monday 01 November 2004 15:52, Henrik Brix Andersen wrote:
> Hmmm... tough question. Currently 729 ebuilds in the portage tree uses
> ${KV} and only 57 use ${KV_PATCH}. It seems that many ebuilds rely on
> knowing the kernel version but not many rely on knowing the kernel
> version in details.
That isn't exactly the point here - portage does parse out all of those things
in order to construct $KV anyway, so could very easily be extended to also
provide $KV_MAJOR etc etc. Regardless of numbers, where do you feel is the
better place for parsing the kernel version details?
I'm in favour of the eclass, I don't think it makes sense for portage to find
the version string on emerge of every package. And, in situations like this
(with localversion appearing) its easier for us to extend the code to support
it.
Daniel
--
gentoo-dev@g.o mailing list
|
|
