From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New cyclic dependency
Date: Wed, 15 Apr 2020 21:28:29 +0200 [thread overview]
Message-ID: <20200415192829.KbDwSYxjuc9zhlBKnbDKWiwXgJMWgnQNljwqyGkytsE@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: 501 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/20438#issuecomment-614235658
Comment:
> build cycles should not be workarounded, they must not exist at all.
but it's not a real build cycle... building all dependencies (runtime too) first is probably simpler but not the best solution imho. My proposal seems simple enough, why is it bad? Splitting packages is also a not very elegant workaround, they must be kept in sync manually and such...
next prev parent reply other threads:[~2020-04-15 19:28 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
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 [this message]
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=20200415192829.KbDwSYxjuc9zhlBKnbDKWiwXgJMWgnQNljwqyGkytsE@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).