[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] installer and director
- From: Jeff McAffer <jeff@xxxxxxxxx>
- Date: Wed, 03 Sep 2008 12:16:24 +0100
- Delivered-to: firstname.lastname@example.org
- User-agent: Thunderbird 126.96.36.199 (Windows/20080708)
Yes, the installer and director are very similar. IMHO these should
combined somehow. The challenge will be to keep the installer simple.
The idea there is that it is really just an example of what you could
do. We are not looking to make it be the all singing all dancing
installer to beat all installers. Having said that, the director is
also similarly simple so combining the two would make sense.
do you have a feel for the functional overlap? Are there things that one
does that the other does?
Another option is to put the headless part of the installer in the
director app (inthe director bundle) and leave the UI part in the
Installer bundle. That way people wanting headless stuff can just use
the director app and the installer becomes a UI thing. This would mean
pushing down a couple things like the install description etc. Not sure
how much code that would be.
Scott Lewis wrote:
I'm working with the installer, with the notion of using it for webapp
I'm aware of the director application and have used it in the past.
Are there any plans to merge the director application and installer
application? In some ways they seem simila...i.e. specifying
artifact, meta-data repos, profiles, etc via command line [director]
or a properties file [installer]...or both using p2 underneath.
Is there any plan/thought/desire to merge them into one
application...or do they have different use cases and/or functionality?
p2-dev mailing list