[Pkg-pascal-devel] compiling packages as user (and autopkgtest)

Paul Gevers elbrus at debian.org
Sat Nov 17 05:59:19 GMT 2018


Hi Abou,

Thanks for your response.

On 16-11-18 21:58, Abou Al Montacir wrote:
> On Mon, 2018-11-12 at 20:44 +0100, Paul Gevers wrote:
>> recently. In my last upload, I revisited the autopkgetest that we (I)
>> have added to the package. While going through some of the (currently
>> accepted) failures, I was wondering what it means if package A depends
>> on package B, both are available, but not compiled by default. It seems
>
> Can you please explain this a bit more? Do you mean that these packages
> are not compiled by the make file upon build of lazarus?

Yes, as discussed already in the past.

>> that $(lazbuild A) fails to find (and) compile package B, even if
>> package B was compiled just before. It seems the logic of lazbuild
>
> So you compiled package B and then try to compile package A that depends
> on B, isn't it?

Well, I just compile ALL packages found in the lazarus tree (see
https://salsa.debian.org/pascal-team/lazarus/blob/experimental/debian/tests/build-lpk-lpi#L20
The order is determined by the find. But in several cases it seems that
package B is compiled before A indeed.

> Did you install the package B first? Please refer to --add-package
> command line option of lazbuild.

No. --add-package is not documented in the man page (in the testing
package). Why would I need to specify this myself? If the dependencies
are correctly documented, lazbuild should be able to figure it out in my
opinion.

>> should grow some "please also look into the $HOME/.lazarus/ folder for
>> the compiled units".
>
> Normally the primary config path is set to this path. So Idon't think we
> need to change anything for that to work. I assume it is only a matter
> of installing the packages using --add-package

So how do I figure out which packages I need to add to the command line
automatically? Can you maybe change the file linked above for me?

> They don't seem to appreciate the
> split on multiple packages and they do distribute their own unique deb
> package.

I haven't checked, but I doubt they build these packages in their own
deb, as these packages are not build by the makefile.

Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20181117/409411b0/attachment.sig>


More information about the Pkg-pascal-devel mailing list