Re: Creating a custom Cygwin package server
Igor Peshansky wrote: upset was a private script that received too much attention at some point, and CGF decided that it wasn't worth making a public open-source project. Also, upset's functionality was much broader than just generating setup.ini. Thus genini, written for that express purpose. Yes, genini has no documentation, but, IIRC, CGF will consider patches to it (including documentation patches). So, it has the potential of becoming *the* way of generating setup.ini files for custom package servers. Anyone can help out. http://cygwin.com/acronyms/#PTC. HTH, Thank you, that's a useful perspective. Hint well taken. I'll try using it and see how much I can offer in the way of documentation. -Norton -- 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: Creating a custom Cygwin package server
Joshua Daniel Franklin wrote: Just be aware that you are entering unsupported territory, and get upset from: http://xarch.tu-graz.ac.at/publ/cygwin/upset Unsupported means don't ask this mailing list if you have problems. A good alternative might be: You can also use genini which is meant to be used in place of upset and is still supported, or rather it still exists in sourceware CVS. Brian Thank you both for your responses. I appreciate the meaning of Unsupported, and I'm sure there must be some history behind this, but do you mind if I ask why? It seems as though being able to build and distribute packages easily is a very useful feature. Was the dropping of support for upset just a push to move to genini (without any documentation), or is there really some other approach that I should be pursuing? -Norton -- 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: Creating a custom Cygwin package server
On Wed, 22 Mar 2006, Norton Allen wrote: Joshua Daniel Franklin wrote: Just be aware that you are entering unsupported territory, and get upset from: http://xarch.tu-graz.ac.at/publ/cygwin/upset Unsupported means don't ask this mailing list if you have problems. A good alternative might be: You can also use genini which is meant to be used in place of upset and is still supported, or rather it still exists in sourceware CVS. Brian Thank you both for your responses. I appreciate the meaning of Unsupported, and I'm sure there must be some history behind this, but do you mind if I ask why? It seems as though being able to build and distribute packages easily is a very useful feature. Was the dropping of support for upset just a push to move to genini (without any documentation), or is there really some other approach that I should be pursuing? upset was a private script that received too much attention at some point, and CGF decided that it wasn't worth making a public open-source project. Also, upset's functionality was much broader than just generating setup.ini. Thus genini, written for that express purpose. Yes, genini has no documentation, but, IIRC, CGF will consider patches to it (including documentation patches). So, it has the potential of becoming *the* way of generating setup.ini files for custom package servers. Anyone can help out. http://cygwin.com/acronyms/#PTC. HTH, 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: Creating a custom Cygwin package server
On 3/19/06, Norton Allen wrote: The documentation here: http://sourceware.org/cygwin-apps/package-server.html suggests it might be possible to set up a custom Cygwin package server to install a custom app, but it also says the necessary tools are not available. Just be aware that you are entering unsupported territory, and get upset from: http://xarch.tu-graz.ac.at/publ/cygwin/upset Unsupported means don't ask this mailing list if you have problems. A good alternative might be: http://sourceforge.net/projects/cygwin-ports/ -- 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: Creating a custom Cygwin package server
Joshua Daniel Franklin wrote: Just be aware that you are entering unsupported territory, and get upset from: http://xarch.tu-graz.ac.at/publ/cygwin/upset Unsupported means don't ask this mailing list if you have problems. A good alternative might be: You can also use genini which is meant to be used in place of upset and is still supported, or rather it still exists in sourceware CVS. Brian -- 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/
Creating a custom Cygwin package server
The documentation here: http://sourceware.org/cygwin-apps/package-server.html suggests it might be possible to set up a custom Cygwin package server to install a custom app, but it also says the necessary tools are not available. Is it possible to do this? Is there another approach that is more highly recommended for distribution of a custom app? (one too specific to warrant inclusion in the main archive.) Norton Allen p.s. I apologize if this subject has been revisited frequently. I just spent about half an hour searching through the e-mail archives without coming up with any clues. -- 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/
