Re: [A-a-p-user] Using AAP for dependency checking (and possibly resolution) on a non-complied progr
Brought to you by:
vimboss
From: Bram M. <Br...@mo...> - 2006-03-10 10:46:05
|
Gareth Anderson wrote: > > I noticed that the Vi example recipe mentioned a depends: > > > http://www.a-a-p.org/examples.html > > > "DEPENDS =3D gtk>=3D1.2<2.0 | motif>=3D1.2 # GTK 2.0 doesn't work yet" > > > > If you are willing to write Python and improve this part of Aap then > > it will be a good starting point. Otherwise I would recommend not using > > the "port recipe". I implemented this once when I was looking into using > > this for BSD, but have not worked on it since then. There are a few > > parts that are not implemented. Some parts may not work properly, there > > has hardly been any serious testing. > > > > Right, well then I will not use that recipe. > > Do you have a recommendation of how I may go about dependency checking for > programs that should be installed (using AAP, or do you recommend some other > software here...)? > > As thats most of what my script will be doing, checking for versions (thats > the first aim, I'll worry about more advanced stuff later). If you mean dependency checking as in checking if include files changed, Aap will do that perfectly. But I suspect you actually want some kind of automatic configuration. There are a few things in Aap for this, but it's not very advanced. The tool usually used for this is GNU autoconf. But it's complicated, requires good knowledge of shell commands and M4, easy to make mistakes both by the author and by the user... I'm still hoping someone will extend the ":conf" stuff in Aap, that will help a lot of people. Then you can use Python instead of M4 and Shell commands. -- From "know your smileys": :-& Eating spaghetti /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://www.ICCF.nl /// |