mrBen
03-14-2001, 09:50 AM
OK - am looking for some feedback on an idea that myself and a friend have got for a new Linux prog. It's mainly my idea, but he would probably use it for his degree project. What we really need to know is if there is something already like this (I don't think so), and any ideas you might have for such a program. Here's the idea, as copied from an e-mail I sent to another guy.
I am somewhat a newbie in the Linux world, although I have come through a fair few obstacles, and am finally able to pass on some 'wisdom' :) to others. However, the area of installing source code has always been a bit of a problem. I can do the tar -zxvf with my eyes closed, and ./configure; make; make install is perfectly understandable, but never seems to go quite how I want it to.
RPMs have been good, both on the command line and in KPackage. But as I understand it, there is an advantage to compile source code on your machine, rather than using the precompiled binaries. Herein lies my suggestion:
I would like a program that would handle the unpacking, verfiying of dependancies, and compilation of source code. This would be acheived by taking details from a simple text config file, and input from the user, and matching these by inserting the correct details allowing ./configure; make install; make to work properly.
The program starts by asking for the path of the .tar.gz / tar.bz2 file. It then (preferably without unzipping the file yet) reads the config file (see below) which supplies it with various details. Then it will ask the user where the program is to be installed to.
Next it will list the dependancies with some extra details:
<Name of dependancy> <where found (if found)> <menu of suggested locations to install from> <browse and install buttons for dependancy>
This page would show if dependancies have been found on the system, and would allow the user to input where to look for them, but also the option to install the dependancy from a location either specified by the programs author or by the user. Once the user has all dependancies satisfied, then installation will go ahead, with any error messages 'explained' for the user.
The program would hopefully be able to scan an ordinary configure file and guess dependancies. Plus we plan to use a web based html/java/script program that allows a developer to enter all the details of his program and have his 'install-config' file outputted for him.
_The 'Install-Config' File_
This would be a simple text file which is placed with all the rest of the source in the tarball. It would go something like this.....
[Title]
title="My Fabby Program"
intro="A fabby program that does lots of cool stuff"
author="Mr V. Clever"
website="http://www.address.com"
bug email="bugs@addresss.com"
[Install]
default="/opt/prog/"
[Dependancies]
no_of_dep=3
[1]
dependancy="libqt"
default="/usr/lib; /usr/X11/lib/"
install="ftp://ftp.address.com; ftp://ftp.mirror.com"
<NB - this would allow companies to provide and install libs off the CD if necessary. User could also enter address of CD if he has one, or search a CD to find if he has it>
Anyway, I hope that gives you some idea of what we're planning. Looking forward to hearing your ideas/comments.
(Please don't hurt me if this is all crap :()
I am somewhat a newbie in the Linux world, although I have come through a fair few obstacles, and am finally able to pass on some 'wisdom' :) to others. However, the area of installing source code has always been a bit of a problem. I can do the tar -zxvf with my eyes closed, and ./configure; make; make install is perfectly understandable, but never seems to go quite how I want it to.
RPMs have been good, both on the command line and in KPackage. But as I understand it, there is an advantage to compile source code on your machine, rather than using the precompiled binaries. Herein lies my suggestion:
I would like a program that would handle the unpacking, verfiying of dependancies, and compilation of source code. This would be acheived by taking details from a simple text config file, and input from the user, and matching these by inserting the correct details allowing ./configure; make install; make to work properly.
The program starts by asking for the path of the .tar.gz / tar.bz2 file. It then (preferably without unzipping the file yet) reads the config file (see below) which supplies it with various details. Then it will ask the user where the program is to be installed to.
Next it will list the dependancies with some extra details:
<Name of dependancy> <where found (if found)> <menu of suggested locations to install from> <browse and install buttons for dependancy>
This page would show if dependancies have been found on the system, and would allow the user to input where to look for them, but also the option to install the dependancy from a location either specified by the programs author or by the user. Once the user has all dependancies satisfied, then installation will go ahead, with any error messages 'explained' for the user.
The program would hopefully be able to scan an ordinary configure file and guess dependancies. Plus we plan to use a web based html/java/script program that allows a developer to enter all the details of his program and have his 'install-config' file outputted for him.
_The 'Install-Config' File_
This would be a simple text file which is placed with all the rest of the source in the tarball. It would go something like this.....
[Title]
title="My Fabby Program"
intro="A fabby program that does lots of cool stuff"
author="Mr V. Clever"
website="http://www.address.com"
bug email="bugs@addresss.com"
[Install]
default="/opt/prog/"
[Dependancies]
no_of_dep=3
[1]
dependancy="libqt"
default="/usr/lib; /usr/X11/lib/"
install="ftp://ftp.address.com; ftp://ftp.mirror.com"
<NB - this would allow companies to provide and install libs off the CD if necessary. User could also enter address of CD if he has one, or search a CD to find if he has it>
Anyway, I hope that gives you some idea of what we're planning. Looking forward to hearing your ideas/comments.
(Please don't hurt me if this is all crap :()