On Fri, Aug 23, 2013 at 8:15 AM, Guillaume Rousse <guillomovi...@gmail.com> wrote: > Le 22/08/2013 14:15, Andres Riancho a écrit : >> As I said in other emails, if you're interested in having support for >> your specific distribution, let me know which packages are needed and >> I'll create a "mageia" file in the platforms directory to handle it. > I don't need any specific software support, I just need clear > indications of actual dependencies. > > [..] >>> I understand perfectly that you are trying to make life easier for >>> newbies, but you're currently making life harder for packagers, by >>> trying to handle their work directly. Before trying any kind of software >>> based solution, with all associated error risks, you should really >>> ensure your documentation is correct, and can be used as a reference. >>> Because your current method seems closer from the problem than from the >>> solution for me :) >> >> Happy to help you in any efforts to create a package for 1.5 and/or >> create a mageia.py inside "platforms". Both things would help our >> users. > I'd happily contribute a documentation patch, but I have very few > interest for such kind of software-based attempt to emulate packager > added value. Giving clear instructions will help users better than > trying to guess what command they have to run. Especially given your > user base: you're not targeting average joe user, after all.
I think both things would be the ideal thing to have: #1 Software dependency package with version (agnostic of any apt/rpm/etc.) #2 The command to install it If we would just provide #1 then people would have to loose time looking for the right command to install it on their systems. Because we do have more users than packagers, I decided to go with #2 and figured out that packagers would take the hit to find out #1 based on that. Also, since packaging is usually a difficult and lengthy process (which might require our dependencies to become other packages, licensing issues, etc.) I also think that #1 is a great idea and won't deprecate it for now. Of course, if you have any better solution, let us know! > I've fixed the check issue by removing calls to dependency_check: > http://svnweb.mageia.org/packages/cauldron/w3af/current/SOURCES/w3af-1.5-no-runtime-dependency-check.patch?view=markup > > Mageia 4 will have w3af version 1.5, mageia 3 already has version 1.1. Removing the dependency check is fine if you package w3af and reference each dependency in the package. Otherwise, as you already know, it will break. If your package was already created, I can "reverse engineer" that into creating a new mageia.py inside "platforms" which will help users trying to install the next version of w3af in their system, a next version that might have a new dependency (which I'll add to mageia.py) before the next w3af release is made. Regards, > -- > Guillaume > > ------------------------------------------------------------------------------ > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > _______________________________________________ > W3af-develop mailing list > W3af-develop@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/w3af-develop -- Andrés Riancho Project Leader at w3af - http://w3af.org/ Web Application Attack and Audit Framework Twitter: @w3af GPG: 0x93C344F3 ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop
