op-panel and libswl-perl
Kilian Krause
kilian at debian.org
Thu Jun 22 20:54:23 UTC 2006
Stuart,
> I debdiff'd the packages and it looks like there is more out of sync than
> possibly intended. Aside from the .orig.tar.gz files being slightly different
> (there was an update to that file for the -5 package, I know that such a
> thing is unusual, but in this case, it was the correct thing to do).
Not only is it unusal, but with a proper Debian archive, that's plain
impossible to achieve without major breakage. That means, one
time .orig.tar.gz will remain that very same file under that name
forever. There is no way in changing it inbetween. Moreover your -5 .dsc
was pointing to another .orig.tar.gz than you had on the website,
therefore I had to regenerate the tarball anyway.
> Also, the changes to clean seems to leave more things in your diff file that I don't
> think need to be there (mostly the autofoo related files).
Sure, was just a quick hack. Great to see you're paying attention to
that.
> There are some additional, unusual dependencies in the makefiles because
> ming doesn't really use the autofoo stuff everywhere like most other projects.
Nothing I would have introduced.
> So far, it's just used to set up a Make.config file, which gets included in
> most of the other makefiles. This Make.config file has dependencies that
> sometimes trigger the running of configure, even if you are trying to just
> do a "make clean". Invoking the 'clean' target in debian/rules multiple times
> causes "make clean" to get executed after "make distclean", which removes the
> files that Make.config depends on (which triggers the execution of ./configure).
Yes, I spotted that. Thanks for the explanation. Surely the update
should be done in a way, that allows the clean target to run without
configure.
> I don't think this happens normally, and if it does, I'm pretty sure it doesn't
> hurt anything, and doesn't take very long. Is some tool or builder causing
> this to show up?
Well, it's ugly as hell, thus it should be avoided if possible. Surely
that requires that one's spotted the source of the Make.config update
first. ;)
> Other than the changes to the 'clean' target in the rules file, I don't see
> anything else that isn't a side effect of that change.
Good. That means, we're up to the point of needing ming-fonts next. ;)
--
Best regards,
Kilian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20060622/4864e219/attachment.pgp
More information about the Pkg-voip-maintainers
mailing list