You are not logged in.
Pages: 1
Hi, I was compiling a kernel last night which I thought was based on 2.6.28-rc9 http://tirdc.livejournal.com/ but it's actually 2.6.29-rc2. So my PKGBUILD had the wrong version number in a few places but it still compiled. The only problem is my pkg/lib has the directory 2.6.29-rc2-ARCH-dirty. What does the dirty mean? I assume it's put there by arch because it comes after ARCH. Does it mean the PKGBUILD made the wrong guess as to the version, or could it mean there were serious compile errors?
6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.
Offline
the -dirty suffix comes from linux-kernelversion/scripts/setlocalversion.
(grep -R is the shiz-nit for tracking shit down in the kernel source.)
i haven't studied it in depth, but the suffix is appended in three different possible places, each one commented with '# Are there uncommitted changes?'.
so, it's not arch's doing, and it's not a sign of serious error.
[23:00:16] dr_kludge | i want to invent an olfactory human-computer interface, integrate it into the web standards, then produce my own forked browser.
[23:00:32] dr_kludge | can you guess what i'd call it?
[23:01:16] dr_kludge | nosilla.
[23:01:32] dr_kludge | i really should be going to bed. i'm giggling madly about that.
Offline
Pages: 1