2012-05-10 12:39 Gergely Nagy <[email protected]>:
| On Thu, May 10, 2012 at 11:28 AM, Jari Aalto <[email protected]> wrote:
|
| > 2012-05-10 09:07 Gergely Nagy <[email protected]>:
| > | Jari Aalto <[email protected]> writes:
| > |
| > | > The only solution I can think of in situation where package "wine" does
not
| > | > exists in system, is to download winetricks directly from the project's
| > | > version control.
| > |
| > | There's another option: faking a wine package. The equivs package comes
| > | handy in cases like this.
| >
| > Nice.
| >
| > The *-4 release of winetricks will have depends on "wine-dummy" with these
| > instructions in package Description:
|
| No need to. wine | wine-unstable is fine, you can use equivs to create
| dummy packages named wine or wine-unstable, and all will be well.
|
| Depending on packages outside of the archive (even if it's only one of
| the three possibilities that satisfy a depends) is frowned upon in the
| best case.
|
| I do not think there is anything that needs to be changed in winetricks.
Actually I could create new package in winetricks::debian/control:
winetricks-wine
And add depends
Depends: winetricks-wine | wine-unstable | wine
To make "wineticks" self sufficient as it was for users that install wine
from sources.
What do you think?
Jari
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
