1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL

  • BuildProfileSpec example equivalence question

    From =?utf-8?Q?Ferenc_W=C3=A1gner?=@21:1/5 to All on Sat Oct 12 20:00:02 2024
    Hi,

    The third example on https://wiki.debian.org/BuildProfileSpec is:

    Build-Depends: foo <nocheck cross> <nocheck>

    In this case, the source package would build depend on foo if either
    both, nocheck and cross are active or if the profile nocheck is
    active. [...]

    This is fully consistent with the definitive part above it, but isn't
    this equivalent to the simpler Build-Depends: foo <nocheck>? If so, I'd
    rather use a different example which does not have this confusing
    property. Or do I miss something here?
    --
    Please keep me in Cc,
    thanks,
    Feri.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Timo =?utf-8?Q?R=C3=B6hling?=@21:1/5 to All on Wed Oct 16 10:10:02 2024
    Hi Josch,

    * Johannes Schauer Marin Rodrigues <josch@debian.org> [2024-10-16
    * 09:21]:
    The third example on https://wiki.debian.org/BuildProfileSpec is:
    I now changed the example to one that is actually used in the wild.
    I hope I didn't mess up the wording. Hope this makes things
    clearer.
    The final sentence in the explanation states that the build profile restrictions are a conjunctive normal form expression; is that
    actually correct?

    Because CNF would be the AND'ing of OR's, but if I understand it
    correctly, the terms *inside* the angle brackets are AND'ed and the
    brackets themselves OR'd, which makes it a DNF, *disjunctive* normal
    form.


    Cheers
    Timo

    --
    ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮
    ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │
    ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │
    ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmcPcpgACgkQzIxr3RQD 9MpsRA//dB72tua68097k0wdxpg/ZVh9Udh/P22nY4dk4RVPIz4K+1mZMV6Cij2R QvyKvq4rAlWcaMmZP3a8Pug2c7vPVZSVo3XMU+bTgnDefvHvJRKaB88+alDgk2Wk BDMP2w49HBj3gY8JVbgV0FP8dqYmv2MvQpvWjN4qGvqzScSVXaFTAJijbEWzSwCQ N3dbBH32oKDOXliNUBr7UrLdAxNyZeBq2vBWIRnEFLY7Rkz9g6cv5RKYrfNAxrsI GyJJCwCDhbNpdQ+qg+ChjOBkuAxIqDtiIuneULHwlNOX8sIDn/vpDB1D4GCBOUTm geK5P1YoyzP4lCfO//WZQJuqBH1xyOunpxPXumUh9ty
  • From Johannes Schauer Marin Rodrigues@21:1/5 to All on Wed Oct 16 09:30:02 2024
    Hi Feri,

    Quoting Ferenc Wágner (2024-10-12 19:39:27)
    The third example on https://wiki.debian.org/BuildProfileSpec is:

    Build-Depends: foo <nocheck cross> <nocheck>

    In this case, the source package would build depend on foo if either
    both, nocheck and cross are active or if the profile nocheck is
    active. [...]

    This is fully consistent with the definitive part above it, but isn't
    this equivalent to the simpler Build-Depends: foo <nocheck>? If so, I'd rather use a different example which does not have this confusing property. Or do I miss something here?

    I now changed the example to one that is actually used in the wild. I hope I didn't mess up the wording. Hope this makes things clearer.

    Thanks!

    cheers, josch
    --==============48129161903996462=MIME-Version: 1.0
    Content-Transfer-Encoding: 7bit
    Content-Description: signature
    Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmcPaWkACgkQ8sulx4+9 g+HQOhAArTdwIJagmEDZLOZebXeio25aFF8pL61AyxUtNJ/W41VJ2aQFi6ut0aXb 2CJ0XtMwy+uSXXXXHew7zLqOVcUssH83HHmvy+6cWOq3I79+cFtW8/glcUCt/Dx5 gwilATw2M7cHzfhi3CR/u4eQWsv6UUYuXDt0jelfg1ysMlGx6eIzL59D4dtZI/Q3 JaXQfn+zgKV61T8Uasm8Sx7lQxH8S3HrgJyGWLEGMtifWQQfqqXtRUBh6Y83svhC F+hZaLD+fU8QcPHZh79c+mr/ye5o8nGjpj8toEpno2+NM7t8rOdcuWepbBOBC3bp T7xBqx04ax/ryjX5rDDvwBMhIK7w7lzGAtYKeCvDbRDeN2lMkrglZ2cs7MAFVijp tLAvht5O22k47gtnx8QW1gjn3Luhqn3d05tJT+zf0KvofofXKOz986tW90hV1TYX 8ssc7u9n0kgXNHdSFGB5rKR8GRg2XuyfS2VJEpIOVCVTFXwCfnXckynBUpWTUIgD R5xh54FWjfw3ylBYs3744ZfJF7JVPjM7SmaDg3LZVv/LfgApSlyWG+OlUKiDk9O7 LrmtCHL1vCkTEdSJtK4M3tKp6wWPEgyqMmFIlMYJQh9Zr0Ui0WG4PHMWRlUVM+jG GZ02koJ7bAiVSRxCUlR1W6OvrMPiB6oEhKPCvLrJ61IzppopC7I=
    =6cqM
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Johannes Schauer Marin Rodrigues@21:1/5 to All on Wed Oct 16 22:20:01 2024
    Hi Timo,

    Quoting Timo Röhling (2024-10-16 10:00:25)
    The third example on https://wiki.debian.org/BuildProfileSpec is:
    I now changed the example to one that is actually used in the wild.
    I hope I didn't mess up the wording. Hope this makes things
    clearer.
    The final sentence in the explanation states that the build profile restrictions are a conjunctive normal form expression; is that
    actually correct?

    Because CNF would be the AND'ing of OR's, but if I understand it
    correctly, the terms *inside* the angle brackets are AND'ed and the
    brackets themselves OR'd, which makes it a DNF, *disjunctive* normal form.

    thank you for spotting that issue. It absolutely is a DNF. And what's even worse, there is another place in the document where it says it's a DNF and not a CNF. Ouch! Thank you for spotting this!

    cheers, josch
    --==============696567415198082392=MIME-Version: 1.0
    Content-Transfer-Encoding: 7bit
    Content-Description: signature
    Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmcQHwEACgkQ8sulx4+9 g+GfDA/8DvJwYkpPajSUNMtHtO/HsNZsblmw7BLuQak7cCU2KXwsLaofI8ydX+DF doTdBtgrNAQPapq+Ol5DtBBwfcfz4/5OH+Lsg2XmV2PPvQ1L+Bf1GW1WQMhSHSwQ ARy9noy0iyrNVddSkut6vT6vQQQ3iUyFHqZAiNpZ/ZHNfsLVzxiHiGPPwPJ28Hvy nEb+Uc7MEU/1Nuu0PvvobYOJel5eij6oIw+BUj5Hhozl/UFauBBdd9de2k9JH4iP JkJYm+Z0Qed7pXDDxIrojzYpUDprcGNt03N9M7ihzsiEQKs6u4u3o99I5ia2NZyP 7bW+m33jsbYSA07mLpDgFziaiNOyLiylGWoURaqUHkAMq5zsyxxakuq27/iSN7F8 R78kRWIrq54XUsrWzrM1XeESQz2L8tEUXsuAjVfmo7OFAQjeLZnZQI9Yy+B7NtRO C5E/PbF/alxji48xnU9pVye8qm422hZCu59RYfoNjrQHR2FCdGGmQMyM+gKGBn3Z m31iDBLl+/c1MH0EPGC82zCPGg+ceCqu9FyhkID5becDtq3QhKFvgG3U7OqIvPft /1CAvMNP34F7+BH56mHS62QO9CbcJwpB6VrlGWmQ35XxnEgLl+yg0aBcMNjQNB58 0ZruvzIjSeL5K6Kr18mWQQyIVibYU9xhsF6hs9iUhVPCqGmQSfY=
    =Mnho
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)