[wpkg-users] [Bug 149] Specify prerequisites for a package

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=149





--- Comment #4 from Erik Langeland <erik.langeland at silvacom.com>  2009-03-30 21:09:40 ---
(In reply to comment #2)
> Actually the point is a different one. Some people would like to see every
> possible feature packed into a single script which in turn gets unmaintainable
> and extremely complicated (to program AND to use).

The way i pictured this is, I think, a bit simpler than what you are describing
here. What I imagined would be to either extend the existing <check ...>
element (such as <check type=install ...> and <check type=prereq ...>) or
create a new element (such as <prereq ...>) with the same check types available
as for the existing <check ...>.

I think this would add a significant amount of functionality while avoiding
your concern of bloating the script by adding too many features, since it
should be able to leverage the existing code that processes the <check ...>
elements.

I have tried the method of using the existing check element to detect the
platforms or scenarios where that package should not be installed. While it
works well when installing the package, when the time comes to remove the
package, the package always detects itself as installed, so it is never
automatically removed.

I will look at your suggestion of having the install scripts check the Windows
version, but that will only work, I think, if it is something that has versions
for all the different Windows platforms. I am also thinking of software that is
only for a specific version of Windows (e.g. some of the Windows XP Power Toys)
and has no equivalent for other Windows versions. In these cases the package
prerequisite would work better.

Erik


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.