search

cckec / winetricks

Automatically exported from code.google.com/p/winetricks
0 stars 0 forks source link

wishlist: do not hard code URLs in the program (separate config) #262

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
PROBLEM

r903 2012-08-21 daniel.r.kegel shockwave: updated....
r902 2012-08-21 daniel.r.kegel wmp10: correct url
r901 2012-08-20 daniel.r.kegel ...
r900 2012-08-20 daniel.r.kegel mfc40: updated url
r899 2012-08-19 daniel.r.kegel jet40: use temporary url while looking for more 
definitive one
r898 2012-08-19 daniel.r.kegel crypt32: update url.
r897 2012-08-18 daniel.r.kegel wininet: update url...

As winetricks is distributed as a package e.g. in Debian and Ubuntu, the users 
cannot be expected to download the latest version directly from Svn to keep up 
with the changing URLs. This not winetricks' fault, just the problem with the 
Internet.

SUGGESTION

Please consider separating the (a) functionality of the program from the (b) 
list of URLs. The currently used METADATA would be candidate for moving to a 
separate file:

   title: <data>, publisher: <data>, year: <data>, media: <type>, file1: <name>, installed_exe1: <windows path>, homepage: <url> ...

The program would work as follows:

- At start, the program would check if WINECONFIG file exists. If not, it would 
download the latest file from winetricks' Code.Google HTTP accessible page.
- When user requests a package to download, it would consult WINECONFIG
- If there is an error while trying to download a package pointed by WINECONFIG 
URL, display an error message indicating that user might need to update 
WINECONFIG for latest URLs.

Updates to WINECONFIG could be requested separately with:

  winetricks --config-update

BENEFITS

Updates only need to be contributed to separate config file, not to the code.

Users are always up to date and do not need to wait until distribution updates 
winetricks. Consider that stable Linux releases do not even change in years. 

ENVIRONMENT VARIABLES

WINECONFIG, if not defined, would default to $HOME/.winetricks/config. Using a 
separate directory allows extending the program in the future and be in par 
with current use separate directories for programs: $HOME/.emacs.d/* .git/*, 
$HOME/.bazaar/* $HOME/.wcd/* etc.

Original issue reported on code.google.com by jari.aalto.fi@gmail.com on 25 Aug 2012 at 6:45

GoogleCodeExporter commented 8 years ago 
Updating URLs is often not enough.  The verb often needs other tweaks.

One of the design goals of winetricks was that it be extremely trivial
to distribute and use.  That's why it's a single file.
When it was rewritten to make verbs stand alone, I made it possible to
load verbs from a separate directory, partly for the purpose of supporting
updates.  So if you want to propose something, that route is probably more
productive.

Original comment by daniel.r...@gmail.com on 25 Aug 2012 at 2:43

GoogleCodeExporter commented 8 years ago 
WONTFIX.

Original comment by austinenglish@gmail.com on 29 Jun 2013 at 1:50