Julian and Tommy, Julian Andres Klode: > That's what I would like to have, too. Just do it like udev, use 001 for th= > e first version, 002 for > the next, etc. Or simply use 0.1, 0.2, 0.3, etc. These are all good version= > numbers (the 2nd type is > actually better because you can have a version 1.0 later [which in the firs= > t case won't work because > eg. 002 > 1.0]). > > We just want a normal tarball, with the code. We want to build it externall= > y. That's > everything.=20
I might misunderstand you. I thought you just wanted both of aufs2-baseN.tar and CVS (or GIT). I almost replied to you saying,,, just run 'patch aufs2-baseN-2.6.xx.patch' under an empty dir, and you would get source files. I will find a public GIT space somewhere, put aufs2 there, and tell you the url. Until then, please just hold on. And I thought everyone can be happy. But you and Tommy are wanting an external module aufs.ko, aren't you? It is not a matter of how I release aufs2. I should write about it in the release note. Aufs2 is not able to be an external module. Users have to configure CONFIG_AUFS_FS=y instead of =m. This is the bigger problem for you, isn't it? Even if I make a public GIT tree, you would not be satisfied as long as you have to set =y. Right? ---------------------------------------------------------------------- "Tommy[D]": > Additionally, the naming is also badly choosen, if someone wants to packa= > ge it, since e.g. > aufs2-base1-2.6.28 would be below the actual 2.6.27 release because of th= > e sorting of the version > string. Do you mean aufs2-2.6.xx-baseN is better? By the way, I don't have a plan to release aufs2-base[1-3]-2.6.2[89]. The 'baseN' is the version of aufs2, and '-2.6.xx' just shows the base version of patches. > Can you create a package similar to the previous cvs source, which people= > can simply unpack, build > against their kernel and then load as module including a better versionin= > g? Currently I am facing toward GIT. If I make a public GIT tree and create two branches, is it enough for you? - branchA equivalent to current aufs2 tarball - branchB for building aufs2 as an external module which will be branchA plus some changes The GIT tree will include whole kernel source tree. Is it OK? J. R. Okajima ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
