> > > http://developer.mozilla.org/en/docs/Adding_Extensions_using_the_Windows_Registry > > I read that page and i must say: "What the fuck are those idiots doing?" > > The documentation is totally useless and either i'm too stupid to follow > > the incomplete instructions or this just doesn't work. > > Either way i can't get it to work no matter what i try. > The instructions there are pretty good and complete i would say. Just try to > read them from the beginning and then continue up to the very end while > following them. As if i haven't done that already ... Maybe you could enlighten me? Best way would be a working example of how the registry entry should look like ...
> How would this make things easier? Your only gain is by getting rid of some > <package> beginning and end tags at the same time introducing aditional check > and install id tags. This only complicates matters and makes packages.xml > editing more prone for errors. The Firefox Extensions are just an example. Just think about Windows or MS Office Updates. You DON'T want to have a package entry for every single entry. Each time a new update comes out you'd have to add it to packages.xml and then edit profiles.xml too. With multiple checks/installs per package you'd only have to edit packages.xml. And if you have a webinterface to edit it the chance to mess it up doesnt increase at all too. - jens ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ wpkg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wpkg-users
