I agree. The installer in headless
mode is essentially the same as the director application and we should
avoid the duplication and confusion of having two command line applications
that do the same thing. I think the only benefit of the installer
is the concept of the install description for encapsulating the application
inputs. The director application instead has a large list of command line
arguments for providing the necessary inputs, which can be quite unwieldy
to use. It would make sense to me to push the install description down
to the director.app bundle to make it easier to use. We would then have
the director app as the standard headless installer, and leave the installer
app as a simple prototype of a GUI-based installer.
Jeff McAffer wrote on 09/03/2008 07:16:24 AM:
> Hey Scott,
> Yes, the installer and director are very similar. IMHO these
> combined somehow. The challenge will be to keep the installer
> 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
> also similarly simple so combining the two would make sense.
> do you have a feel for the functional overlap? Are there things that
> 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
> the director app and the installer becomes a UI thing. This
> pushing down a couple things like the install description etc. Not
> how much code that would be.
> Scott Lewis wrote:
> > Hi folks,
> > I'm working with the installer, with the notion of using it for
> > update/install.
> > I'm aware of the director application and have used it in the
> > 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?
> > Thanks,
> > Scott
> > _______________________________________________
> > p2-dev mailing list
> > p2-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/p2-dev
> p2-dev mailing list