Well that was a little bit mellodramatic (IMHO, like everything I say is ;-)
But do you envision software being shipped at some point expecting to be installed with your install package?
Does it matter?
It's a great pet project to stretch out them brain muscles, and at least two "developers" will be using it (Jouke and I).
Do you expect companies who do that to go through the effort of also providing .rpm and .deb format installs that they have tested? Realistically I don't think that will happen. It would be great if it did, but I try to be realistic about these things and I just don't see them doing that duplication of work just because some tech thinks other techs would like it.
What's he got to do with *companies* or other format installs?
I don't think you're trying to be realistic. If companies want to truly promote their product, they'll provide it in every format possible, after all, I doubt they'd want to lose potential sales, for a few hours extra work.
I would like to see the GUI install not come into conflict with existing and accepted methods of installing and managing software.
has no control over that, nor should that be his concern (he's not Bill Gates).
That is my concern. Personally if I have a choice, I will not use software on Linux that requires a pretty GUI installation. It is something that I hated about Windows, and with apt and friends I have no shortage of software that I like which doesn't force me to sit like a monkey and click buttons. (Or force me to do undue work trying to script an installation that was clearly designed for marketing and not for a tech.)
For these reasons and more, the way that I would like to see this itch scratched is in defining hooks in the .rpm or .deb format which allow someone to distribute software in an accepted format which will, if installed with an optional front end, give people a nice graphical installation. That is, instead of creating a portable tool in which people define their install-shield like install once and say, "OK, that is it for all of our platforms" (leaving me a second class citizen) I would like to see the GUI install not come into conflict with existing and accepted methods of installing and managing software.
My sentiment exactly, but, what are the chances of Jouke
actually getting the developers .rpm and .deb to add these hooks. He shoud make the suggestion, as should you, but this is all besides the point.
I suggest that Jouke provide some kind of a "non-interactive" switch option, where the default setting will be applied, and the user won't be prompted, or some type of "config-file", which would also be non-interactive, but the config options would be read from a file.
This would of course be an *additional* feature down the road.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||