Github messages for voidlinux
 help / color / mirror / Atom feed
From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New cyclic dependency
Date: Mon, 30 Mar 2020 01:33:13 +0200	[thread overview]
Message-ID: <20200329233313.iIKZpy2tAjKi3ZzuKB-1ZbuNOILrWVSi6RuQwiGu5q8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20438@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]

New comment by st3r4g on void-packages repository

https://github.com/void-linux/void-packages/issues/20438#issuecomment-605719104

Comment:
I think `xbps-src` could be improved to handle such a scenario, which is not so uncommon. For example, `libglvnd` needs at least one GL vendor to work, but adding `depends=mesa` would introduce an endless loop at the moment.
One could detect the loop and break out of it, but it doesn't feel very elegant. Instead, what about making `xbps-src` build all the runtime dependencies **after** their "parent" package (i.e. the one that is being built)? I did a little experiment in this branch: https://github.com/st3r4g/void-packages/tree/xbps-src-rdeps
Obviously this is not feasible right now, as packages would be added to the index before some of their dependencies are built. But I believe this could work with a better staging mechanism, handled outside of `xbps-rindex`.
The current staging mechanism cannot handle multiple repositories, so it needs to be improved anyway. It was proposed something like: `xbps-rindex` always stages, a new tool (multirepo aware) checks for publishing the packages that are ready (shlibs and runtime deps checks).

  reply	other threads:[~2020-03-29 23:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 10:12 [ISSUE] " pullmoll
2020-03-29 23:33 ` st3r4g [this message]
2020-04-15 15:11 ` xtraeme
2020-04-15 15:18 ` xtraeme
2020-04-15 15:37 ` xtraeme
2020-04-15 15:39 ` xtraeme
2020-04-15 15:42 ` [ISSUE] [CLOSED] " xtraeme
2020-04-15 19:28 ` st3r4g
2020-04-15 19:28 ` st3r4g
2020-04-15 19:35 ` xtraeme
2020-04-15 19:36 ` st3r4g
2020-04-15 19:37 ` st3r4g
2020-04-15 19:37 ` st3r4g
2020-04-15 19:38 ` st3r4g
2020-04-15 19:39 ` st3r4g
2020-04-15 19:40 ` st3r4g
2020-04-15 19:58 ` xtraeme
2020-04-15 20:00 ` xtraeme
2020-04-17 16:12 ` Chocimier
2020-04-17 16:35 ` st3r4g
2020-04-17 16:37 ` st3r4g
2020-05-17  9:17 ` st3r4g
2021-02-05  3:36 ` Can xbps-src work around runtime cyclic dependencies instead of requiring manually split templates? ericonr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200329233313.iIKZpy2tAjKi3ZzuKB-1ZbuNOILrWVSi6RuQwiGu5q8@z \
    --to=st3r4g@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).