On 14/01/2008, Giancarlo Niccolai wrote: > Yes, they could; but the build process is quite customized. Source > comes from three sub-projects that are kept separate for > administrative reasons, but are integrated at operating level. I read > in the debhelper and related manual that it may have some trouble in > detecting modules which need particular stripping rules, and a very > important part of the base library (which is supposed to support > application embedding scripts) relies on loadable binary modules, as > the RTL.
You can always use parameters to exclude this or that files, using “dh_strip -Xfoo -Xbar”, which might help you target exactly what you want. > If that has to be done manually, then using some automated tools and > not other may mess up things; if not now, they may be in future if new > dependencies are drawn between dh_* tools. OK, thanks for considering. > And anyhow, I may use anything if it simplifies the process and works, > but I'd need assistance, as using such automated (and > documented-through-examples) tools can be problematic when having > custom builds and not a clear picture on how they infer things. I see, I'm not sure I'll find the time to help you do so, sorry. But if you run into troubles trying to, just ask here and see whether someone has a clue. > Oh... so the watch file can refer even an http page linking the packages? -- > where can I find some example? > However, shouldn't it work also on i.e. the http tree at Yes, that's documented in the manpage. The following should do: | http://www.falconpl.org/?page_id=downloads \ | /downloads/([0-9.]+)/Falcon-[0-9.]+.tar.gz Indeed: | [EMAIL PROTECTED]:/tmp/falcon-0.8.7$ uscan --report-status | Processing watchfile line for package falcon... | Newest version on remote site is 0.8.6, local version is 0.8.7 | falcon: remote site does not even have current version Cheers, -- Cyril Brulebois
pgpY6aIlBpB0v.pgp
Description: PGP signature
