[Bug 532230] New: Make 'make paranoid install' run unattended

["GARNOME (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=532230

  GARNOME | general | Ver: unspecified
           Summary: Make 'make paranoid install' run unattended
           Product: GARNOME
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: general
        AssignedTo: garnome-maint gnome bugs
        ReportedBy: cjcollier colliertech org
         QAContact: garnome-list gnome org
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Many dependencies (header files, etc) are not installed on the machine when one
runs 'make paranoid install'.  The user is not notified of this until the
failure occurs.  There is no way to list dependencies that garnome does not
itself handle (usually by including in the bootstrap section).

I propose creating a means by which dependencies can be accounted for, even if
garnome does not directly provide a means by which they may be installed.

The primary problem with this is that many garnome users do not have superuser
access on the machine on which they are using garnome.

Another problem is that there is no canonical way to refer to a package that
persists across all variants of all operating systems.  The closest I can think
of is the filename of the .pc file used with pkg-config.

We also want to start receiving reports of when 'make paranoid-install' fails. 
I further propose that garnome make use of bug-buddy to open a communication
channel with our users.

Some tasks that must be completed in order to allow dependencies to be
correctly handled are the following:

* determine platform and flavor, ie config.guess + /etc/debian_version
* create script to map missing package to dist. package name
* create standard way of defining dependency on package not included in
bootstrap
* when non-bootstrap, not-installed package is missing, add to dist. package
list


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=532230.