[EMAIL PROTECTED] wrote: > Hello everybody... > > I had some trouble with the copy of /usr/src I fetched and so I had to > refetch it. But now I'm not sure if I included all patches (even I've e.g. > no em-Device (Btw: why are just critical patches listed?)). > > I guess there's no "system" to identify if somebody applied a patch or if > he/she dosn't so I thought about a "easy" system wich could be > implemented.
huh? It is trivial to figure out if a patch has already been applied. Hint: Try applying the patch again, see what happens. Why do we need a complicated "system"? If you didn't read the documentation on how updates work, and the difference between patches and -stable, and and and...why do you think anyone else would read the documentation on your "system"? > The ports-tree uses checksums to check the integrety of a port. > So why can't a script include all Checksums for e.g. patches? > > /usr/ports/infrastructure/out-of-date checks e.g. the packages. > Somebody could write a shellscript wich includes the Checksums for a > compiled (and patched) binary for each architecture. E.g. the EM-Driver... > The file includes also just the Checksums for files wich where patched. > > That is (ofcourse) not the "best" solution but it could be implemented > fastly and it would work. > > So if somebody (like me) f**ked up his copy of src he could refetch the > copy and get the latest copy of that script and it would just tell me e.g. > "Checksum for */pci/em missmatch" (I don#t know the complete path so don#t > critic that). Let's see... You want something that will only fetch the files which have been updated. You probably want it to respect any changes in your local tree. Might as well throw in the ability to see diffs between any two versions of a file.. and we now have invented... CVS(1)! (yeah, there are a lot of other features there, too). There already *is* a system... But, you have to read the documentation and learn how other people do things on their project...not just expect them to reinvent the world for how you thought of doing it differently. Nick.
