Messages in this thread | | | Date | Sat, 9 Feb 2002 16:36:03 -0700 | From | Andreas Dilger <> | Subject | Re: [bk patch] Make cardbus compile in -pre4 |
| |
On Feb 09, 2002 13:41 -0800, Larry McVoy wrote: > We don't, but we can, and we should. "bk relink tree1 tree2" seems like > the right interface.
Yes, this would be great. It should probably only do this for files in SCCS and BitKeeper directories, because vim (for example) will do the wrong thing with hard-linked files if you edit them. Maybe there could be another option which would relink all of the checked-out files as well, for people who use emacs?
> Right now we aren't too worried about the disk space, the data is sitting > on a pair of 40GB drives and we're running the trees in gzip mode, so they > are 75MB each. But yes, it's a good idea, we should do it, and probably > should figure out some way to make it automatic. I'll add it to the > (ever growing) list, thanks.
One thing that I've noticed (got my first linux-2.5 clone last night) is that the kernel build process is somewhat broken by the fact that not everything that you need to build is checked out of the repository by make.
It appears to handle .c files ok, but it failed for all of the .h files. I take it this means that gcc doesn't know anything about SCCS, and it would also appear that make is not properly checking dependencies for these files, or it would have checked them out, right?
Also, things like "make menuconfig" and such also fail (because they are doing stuff within scripts that have no concept of SCCS or BK). Will the new kernel build system take any of this into account?
I would prefer if we only checked out as much as we need (instead of doing something like 'bk -r edit' which will use up a lot of space in each clone for architectures and drivers which I don't need).
Cheers, Andreas -- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |