Re: RPM's (was Re: unix 'at' command implementation)
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: RPM's (was Re: unix 'at' command implementation)
Christopher Faylor wrote That's precisely why people think about integrating something like rpm or deb into the packaging system. May be someone has found the right way: cyg-apt. It is in an early stage, does not handle 'in-use' file substitution, but for simple update-upgrade, it works. I'm not saying that tar.bz2 is not a good packaging format, but only point out that now there is no CLI alternative to setup.exe. Administering a Cygwin environment from the command line is better in IMHO. I would hate to see this thread become a wish-fest when there is obviously no one interested in doing this work. My skills are too low to start and finish such a project. I'm not a coder, I'm a SysAdmin... -- Diesis -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: RPM's (was Re: unix 'at' command implementation)
On Sun, Jun 11, 2006 at 02:04:11PM -0400, Igor Peshansky wrote: >Technically, nothing prevents you from shipping a Cygwin package (which is >just a .tar.bz2) that contains only the Cygwin binary RPM and the >postinstall script that invokes "rpm" to unpack that binary RPM (as long >as that package also "requires:" the "rpm" package). You'll also need to >build a manifest of all extracted files and have a preremove script that >cleans those up. See the gcc-mingw-core package for an example of a >similar approach. Nothing would stop anyone from using rpm to build a package and then using "rpm2tar" to convert the rpm to a .tar.bz2 file either. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: RPM's (was Re: unix 'at' command implementation)
On Sun, Jun 11, 2006 at 06:38:49PM +0200, [EMAIL PROTECTED] wrote: >Max Bowsher wrote >>I've entertained fantasies of making integrating dpkg into setup.exe, >>and making Cygwin packages be in .deb format > >I'll certainly love .deb packages, surely apt support. Cygwin is >command-line, so it would be nice to ssh remotely in a machine, run >apt-get update && apt-get upgrade to mantain the Cygwin system That's precisely why people think about integrating something like rpm or deb into the packaging system. However, the funny thing about free software is that no matter how much people want this type of thing it still requires someone to do the actual work. I would hate to see this thread become a wish-fest when there is obviously no one interested in doing this work. That would be a waste of good electrons. I will point out that there is no mystery to the format of cygwin packages. They are just .tar.bz2 files and they are *MUCH* simpler than rpm or deb files (and I am intimately acquainted with all three formats, thanks). It is not that hard to extract .tar.bz2 files and install them except for the chicken/egg problem of installing packages that are used to install packages. That is a basic problem with rpm and deb too. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: RPM's (was Re: unix 'at' command implementation)
On Sat, 10 Jun 2006, Linda Walsh wrote: > Eric Blake wrote: > > > I have cygwin install but I can not find the > > > implementation of Unix 'at' command. > > > > > Because no one has ported an open source version of it > > to cygwin yet. > > > >Some packages might be more easily ported if RPM's > became a common way to package cygwin packages. Much > of the porting effort is in converting to the cygwin installer. > Someone asked about logrotation a while back and I was > surprised no one had ported a logrotate package. I pulled > the source RPM from my SuSE distro, and was able to > produce a binary RPM in about 10 minutes, then I realized > RPM's weren't a desirable format for cygwin packages. Do you mean that you used Cygwin's rpm package to produce that RPM? >I'm sure there's some good reason for converting all > packages to yet another installer, but I'm not sure I know > what they are. One side effect, though -- it can put a > damper on porting programs over when most (or all) of the > work is in converting to the a different installer. Technically, nothing prevents you from shipping a Cygwin package (which is just a .tar.bz2) that contains only the Cygwin binary RPM and the postinstall script that invokes "rpm" to unpack that binary RPM (as long as that package also "requires:" the "rpm" package). You'll also need to build a manifest of all extracted files and have a preremove script that cleans those up. See the gcc-mingw-core package for an example of a similar approach. What you will lose with the above is the ability to list and search package contents via cygcheck and the online package search. Incidentally, one of the things we should teach setup and cygcheck to do is look at the manifest files produced by postinstall scripts and include those in the file lists of the package. I'm sure it would be easier to do than add full dpkg or rpm support to setup.exe, and would be a good way to familiarize yourself with the code of setup/cygcheck. As usual, PTC. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac" -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: RPM's (was Re: unix 'at' command implementation)
Max Bowsher wrote I've entertained fantasies of making integrating dpkg into setup.exe, and making Cygwin packages be in .deb format I'll certainly love .deb packages, surely apt support. Cygwin is command-line, so it would be nice to ssh remotely in a machine, run apt-get update && apt-get upgrade to mantain the Cygwin system -- Diesis -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: RPM's (was Re: unix 'at' command implementation)
Larry Hall (Cygwin) wrote: > Linda Walsh wrote: >> Eric Blake wrote: I have cygwin install but I can not find the implementation of Unix 'at' command. >>> Because no one has ported an open source version of it >>> to cygwin yet. >>> >> >>Some packages might be more easily ported if RPM's >> became a common way to package cygwin packages. Much >> of the porting effort is in converting to the cygwin installer. >> Someone asked about logrotation a while back and I was >> surprised no one had ported a logrotate package. I pulled >> the source RPM from my SuSE distro, and was able to >> produce a binary RPM in about 10 minutes, then I realized >> RPM's weren't a desirable format for cygwin packages. >> >>I'm sure there's some good reason for converting all >> packages to yet another installer, but I'm not sure I know >> what they are. One side effect, though -- it can put a >> damper on porting programs over when most (or all) of the >> work is in converting to the a different installer. > > > Support for RPM and DEB packages were always intended for setup.exe. > It's just no one has added this support yet. Anyone who's interested > is certainly welcome to provide patches to reach this goal. I'm sure > they will be thoughtfully considered. I've entertained fantasies of making integrating dpkg into setup.exe, and making Cygwin packages be in .deb format. It's a pretty huge undertaking though, and somehow I can't see myself getting around to it any time soon. Max. signature.asc Description: OpenPGP digital signature
Re: RPM's (was Re: unix 'at' command implementation)
Linda Walsh wrote: Eric Blake wrote: I have cygwin install but I can not find the implementation of Unix 'at' command. Because no one has ported an open source version of it to cygwin yet. Some packages might be more easily ported if RPM's became a common way to package cygwin packages. Much of the porting effort is in converting to the cygwin installer. Someone asked about logrotation a while back and I was surprised no one had ported a logrotate package. I pulled the source RPM from my SuSE distro, and was able to produce a binary RPM in about 10 minutes, then I realized RPM's weren't a desirable format for cygwin packages. I'm sure there's some good reason for converting all packages to yet another installer, but I'm not sure I know what they are. One side effect, though -- it can put a damper on porting programs over when most (or all) of the work is in converting to the a different installer. Support for RPM and DEB packages were always intended for setup.exe. It's just no one has added this support yet. Anyone who's interested is certainly welcome to provide patches to reach this goal. I'm sure they will be thoughtfully considered. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RPM's (was Re: unix 'at' command implementation)
Eric Blake wrote: I have cygwin install but I can not find the implementation of Unix 'at' command. Because no one has ported an open source version of it to cygwin yet. Some packages might be more easily ported if RPM's became a common way to package cygwin packages. Much of the porting effort is in converting to the cygwin installer. Someone asked about logrotation a while back and I was surprised no one had ported a logrotate package. I pulled the source RPM from my SuSE distro, and was able to produce a binary RPM in about 10 minutes, then I realized RPM's weren't a desirable format for cygwin packages. I'm sure there's some good reason for converting all packages to yet another installer, but I'm not sure I know what they are. One side effect, though -- it can put a damper on porting programs over when most (or all) of the work is in converting to the a different installer. -l -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
