Dan McGee wrote:
On Thu, Apr 16, 2009 at 2:59 PM, Aaron Griffin <[email protected]> wrote:
On Tue, Apr 14, 2009 at 2:29 PM, Aaron Griffin <[email protected]> wrote:
On Tue, Apr 14, 2009 at 2:10 PM, Eric Bélanger <[email protected]> wrote:
On Thu, Apr 9, 2009 at 12:01 PM, Aaron Griffin <[email protected]> wrote:
On Thu, Apr 9, 2009 at 6:39 AM, Allan McRae <[email protected]> wrote:
Aaron Griffin wrote:
On Mon, Apr 6, 2009 at 8:23 AM, Allan McRae <[email protected]> wrote:
How hard would it be to convert from using unionfs to aufs2 in devtools?

Very easy. Minor changes to the mount syntax.

Great.  Any chance of a patch now the kernel without unionfs is in [core]?
 I don't have time to look into this at the moment but would like to
continue using the build tools...
Yeah, I will get to this tonight. I have been slacking way too much
with Arch stuff (been hella busy at work) - it irritates me, so I'm
going to power through a few things I've been putting off tonight.

Both devtools AND archiso need changes, but I also want to get some of
my packages out of the way and finish up the bash rebuilds (mkinitcpio
issue is fixed in one of the official patches, so I'll be pushing out
4.0.17 as soon as I can)

Any update for devtools? I'm still using 2.6.29.1-2 as I want to keep
using my chroots.
If you want to jump ahead:
http://code.phraktured.net/cgit.cgi/devtools/commit/?id=ca87391f99760dc6677df419031108e65b588ecd

The patch is simple, as aufs supports unionfs syntax too. Actually a
sed "s/unionfs/aufs/" should actually work too.

Make sure to install aufs2-util though
Any qualms with me releasing devtools as it is from git?

Yes- it installs a communitypkg script that will no longer work with
the tupkg uploader, as it has been switched to use the devtools and
upload to our other server.

I suppose we can just not distribute that in the package for the time being. Anyway, I will be taking the git versions of the building scripts for a spin later today so I can give them a good testing before you make a release.

Allan



Reply via email to