Paul, First of all, I would like to say that I know that Martin has file an RFH for autopkgtest because he no longer has the time he used to have for its maintenance, so I sincerely appreciate the detailed reply that he sent to me.
On Sat, Aug 25, 2018 at 1:06 PM Paul Gevers <elb...@debian.org> wrote: > > Hi Paul, > > On 25-08-18 03:02, Paul Hardy wrote: > ... > Patches to the documentation are always welcome, especially to cover > blind spots in our minds, even if only to get us in the right direction > of what you are really looking for. However, as Martin already > mentioned, try to do this not too specific for make as there are so many > other frameworks. I would have already done that, but felt anything I wrote would have been conjecture. My stumbling block is that I do not understand all the virtual runtime environments that autopkgtest supports. I can suggest additional text as a patch here, re-opening the bug (I didn't want to do that before). Then you can accept or reject the text I suggest, and close the bug again. > Also, I am trying to collect these kind of things and related stuff > (which may be framework specific) here: > https://wiki.debian.org/ContinuousIntegration/AutopkgtestBestPractices > Feel free to add your remarks there. I will be glad to do that once I think I have my facts straight. In the meantime though, with my less than perfect autopkgtest understanding, I will load experimental packages and make sure the CI stuff works first. Thank you, Paul Hardy
