RE: mkcramfs & mkfs.jffs2 packages
> > Marion, > > > > I'd be happy to work with you on the initial package release, > > and I'm willing to take on maintenance responsibility for them > > after the initial release. > > > Thanks for your proposition. I hadn't realized that an official > maintainer should have been delivered with the package and I'm glad > you're feeling up to do it. Great! > > What versions of these utilities are you working with? > For mkcramfs the original code was taken from ELDK > (cramfs-0.0.1) since > my target is a PPC the tool must have an option to switch endianness. > For mkfs.jffs2 code was taken in the MTD snapshot dated from > 03.12.2004 > (version 1.42). We're using cramfs-1.1 from the sourceforge site, plus patches. The mkfs.jfss2 code shouldn't be too much of a problem, as we're using a snapshot From January of this year, and the only major changes I think we've had to make were just aimed at getting the code to compile under Cygwin. If you can post a link to your sources, I can take a look and see how different they are from what we're using, and see about putting together an initial source and binary package for Cygwin. -Samrobb
Re: mkcramfs & mkfs.jffs2 packages
Robb, Sam wrote: On Tue, Mar 29, 2005 at 02:36:05PM +0200, Marion Deveaud wrote: Unfortunately I have no time to maintain those packages. The most part of the work is to assure the compatibility of the image with Linux filesystems drivers. If you can't maintain the packages then these can't be submitted for the release. Maintenance is part of the deal when you offer packages like this. Marion, I'd be happy to work with you on the initial package release, and I'm willing to take on maintenance responsibility for them after the initial release. Thanks for your proposition. I hadn't realized that an official maintainer should have been delivered with the package and I'm glad you're feeling up to do it. What versions of these utilities are you working with? For mkcramfs the original code was taken from ELDK (cramfs-0.0.1) since my target is a PPC the tool must have an option to switch endianness. For mkfs.jffs2 code was taken in the MTD snapshot dated from 03.12.2004 (version 1.42). We have builds that we maintain internally that include some minor fixes to devtable support that we'd like to see included if these are to become official Cygwin packages. -Samrobb
RE: mkcramfs & mkfs.jffs2 packages
> On Tue, Mar 29, 2005 at 02:36:05PM +0200, Marion Deveaud wrote: > >Unfortunately I have no time to maintain those packages. The > most part > >of the work is to assure the compatibility of the image with Linux > >filesystems drivers. > > If you can't maintain the packages then these can't be submitted for > the release. Maintenance is part of the deal when you offer packages > like this. Marion, I'd be happy to work with you on the initial package release, and I'm willing to take on maintenance responsibility for them after the initial release. What versions of these utilities are you working with? We have builds that we maintain internally that include some minor fixes to devtable support that we'd like to see included if these are to become official Cygwin packages. -Samrobb
Re: mkcramfs & mkfs.jffs2 packages
On Tue, Mar 29, 2005 at 05:49:41PM +0200, Lapo Luchini wrote: >Christopher Faylor wrote: >>>Unfortunately I have no time to maintain those packages. The most part >>>of the work is to assure the compatibility of the image with Linux >>>filesystems drivers. >> >>If you can't maintain the packages then these can't be submitted for >>the release. Maintenance is part of the deal when you offer packages >>like this. > >I guess the best next thing to actually mantain them is to put them on >a *permanent* website and posting a message to cygwin@cygwin.com: maybe >someday someone will find the time to mantain them, but at least people >desperately needing them will found them searching ML archives. Also >structirung the said website with a valid "setup" structure would help >people install/update it, as they could ass the "custom URL" to setup >and not have to install "manually" any package. Or you could add the software to the "Software" section of the web site by filling out the form at the bottom of the page. cgf
Re: mkcramfs & mkfs.jffs2 packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Christopher Faylor wrote: >> Unfortunately I have no time to maintain those packages. The most >> part of the work is to assure the compatibility of the image with >> Linux filesystems drivers. > > If you can't maintain the packages then these can't be submitted > for the release. Maintenance is part of the deal when you offer > packages like this. I guess the best next thing to actually mantain them is to put them on a *permanent* website and posting a message to cygwin@cygwin.com: maybe someday someone will find the time to mantain them, but at least people desperately needing them will found them searching ML archives. Also structirung the said website with a valid "setup" structure would help people install/update it, as they could ass the "custom URL" to setup and not have to install "manually" any package. Lapo - -- Lapo Luchini [EMAIL PROTECTED] (PGP & X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQIcBAEBCAAGBQJCSXkVAAoJELBiMTth2oCDmBwP/1KxRGo5nUKI0deWWLIhIhtW hDmplQd3Wn0zavyRUZStD7Q4tyttAlzqM2c7bbAPA28cztcPnz04jcaaLga1jUfb JDJx0YpLjkNID+wOB4cGAq0d6FbRgnf5FNvZ88iK1k8qoRXhnHjnDzpULmltWcEy oau/I5HzjmqdTm9k9gO3IPGIgk209Vo+4Ae//L+o81SBQpRQIWa0gbmtWVNSVRt+ /GgEnC0cFamVG2M43Lsu/VqZJ+HY/q8/XpSPdgfIG5AG8hmL1xOGgX9peWBSNPpO ptiHNz3d5drSG1Iz1h8g1+XUq92zsuBpHsqV7bCnt41y02Io9zXSTkmj+XdiJGNT Hn7ygNGaGGOgKJdMwHewDeCIFbnrYG51bs59U+mseR1I5NQkIbdkbc9dFLoTBw6g G4EQjcYmdY4q6tMppMeMFkDlCDlNmMWJgV/DX1lwfE6lVQtSYmnSFbLVKy0c5EJp 22Sl7w6ZeNllyhON2IqSDKgAZdiCOMk9qhn5VuLFMtxx5bxiKtoC95tUd7653Aix lQQan8bV86sD73lZ5/oeC5d3H5EXpqiWKx4OHKBaTLSGQCcDEWdH917mnDjfN3HT /iJt8NY/MfaH0OSJLeCYbY4JLQBzTOeupTBi2JIW7Vm0oBpSirV4gdLGkb9V9R5E qO3eSapvuNI06ubcccPp =j88S -END PGP SIGNATURE-
Re: mkcramfs & mkfs.jffs2 packages
On Tue, Mar 29, 2005 at 02:36:05PM +0200, Marion Deveaud wrote: >I had to port those two tools for Cygwin to help my customer develop his >embedded Linux application in the Cygwin environment. Since I sometimes >see on the mailing-list people asking for those tools I though my work >may help other guys out there. > >Here the description of both of the packages: > >mkcramfs setup.hint: >--- >category: Devel >requires: cygwin >sdesc: "A tool to create CRAMFS filesystem images conform to Linux." >ldesc: "A tool to create CRAMFS filesystem images conform to Linux. >Can be used to create embedded (root)filesystem images." > > >mkfsjffs2 setup.hint: > >category: Devel >requires: cygwin >sdesc: "A tool to create JFFS2 filesystem images conform to Linux." >ldesc: "A tool to create JFFS2 filesystem images conform to Linux. >Can be used to create embedded (root)filesystem images." > > >Unfortunately I have no time to maintain those packages. The most part >of the work is to assure the compatibility of the image with Linux >filesystems drivers. If you can't maintain the packages then these can't be submitted for the release. Maintenance is part of the deal when you offer packages like this. cgf
