public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: mtdutils and libubiio
Date: Thu, 07 May 2009 08:57:36 +0300	[thread overview]
Message-ID: <1241675856.27996.8.camel@localhost.localdomain> (raw)
In-Reply-To: <71cd59b00905060522w191f5f19n6c67a1f33a55b061@mail.gmail.com>

On Wed, 2009-05-06 at 14:22 +0200, Corentin Chary wrote:
> Hi,
> You'll find here some experiments:
> http://git.iksaif.net/?p=users/iksaif/mtd-utils.git;a=summary
> 
> Before working on mkfs.ubifs I wanted to cleanup the mtd-utils dir, so
> I tried some change,
> including the use of CMake. As a lot of people here don't want to hear
> about CMake, if the patchs
> for mkfs are good enought, I'll rebase them on a vanilla version of mtd-utils.

I have a pile of patches in my tree as well. I wait for dwmw2 to send
my "export subpage via sysfs" patch to Linus, and after this I'll
push my changes. They basically make libmtd use sysfs interface, but
there are some random minor libubi changes and fixes. I'll try to
push this ASAP.

Vs CMake. I do not know. I'm not very good in this at all. Mike kind
of maintains the build system in the mtd-utils, and he lately improved
it. So if you may convince him, probably. But the thing is that not
many people care about mtd-utils, and if you introduce CMake and then
disappear - who is going to maintain that ?

I personally think that if Makefile can do the same stuff, there is
no reason to change/add new build system only because it is fewer lines
in CMake.

> What you'll find here:
> - CMake "experiment" with dependencies check on zlib and libacl
> - libubiio, provinding the same API the kernel does
> - mkfs.ubifs using libubiio, can write the image directly on an ubi volume

Would you please send patches. It is so much more convenient to
people? Teaching mkfs.ubifs write directly into the volume sounds
nice, BTW.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2009-05-07  5:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-05  9:49 mtdutils and libubiio Corentin Chary
2009-05-05 11:39 ` Josh Boyer
2009-05-05 12:20 ` Mike Frysinger
2009-05-05 12:21 ` Artem Bityutskiy
2009-05-05 12:47   ` Corentin Chary
2009-05-05 12:57     ` Mike Frysinger
2009-05-06 12:22   ` Corentin Chary
2009-05-07  5:57     ` Artem Bityutskiy [this message]
2009-05-07  8:41       ` Corentin Chary
2009-05-07  8:49         ` Artem Bityutskiy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1241675856.27996.8.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=corentin.chary@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox