All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	George Dunlap <George.Dunlap@citrix.com>
Subject: Re: Getting rid of (many) dynamic link creations in the xen build
Date: Thu, 15 Oct 2020 12:49:44 +0200	[thread overview]
Message-ID: <0df66f1c-a02d-819c-0f05-8a7b26728e87@suse.com> (raw)
In-Reply-To: <5c9d5d97-10c4-f5de-e4eb-7ae933706240@suse.com>

On 15.10.20 12:09, Jan Beulich wrote:
> On 15.10.2020 09:58, Jürgen Groß wrote:
>> After a short discussion on IRC yesterday I promised to send a mail
>> how I think we could get rid of creating dynamic links especially
>> for header files in the Xen build process.
>>
>> This will require some restructuring, the amount will depend on the
>> selected way to proceed:
>>
>> - avoid links completely, requires more restructuring
>> - avoid only dynamically created links, i.e. allowing some static
>>     links which are committed to git
> 
> While I like the latter better, I'd like to point out that not all
> file systems support symlinks, and hence the repo then couldn't be
> stored on (or the tarball expanded onto) such a file system. Note
> that this may be just for viewing purposes - I do this typically at
> home -, i.e. there's no resulting limitation from the build process
> needing symlinks. Similarly, once we fully support out of tree
> builds, there wouldn't be any restriction from this as long as just
> the build tree is placed on a capable file system.
> 
> As a result I'd like to propose variant 2´: Reduce the number of
> dynamically created symlinks to a minimum. This said, I have to
> admit that I haven't really understood yet why symlinks are bad.
> They exist for exactly such purposes, I would think.

Another option would be to create the needed links from ./configure
instead of committing them to git.


Juergen


  parent reply	other threads:[~2020-10-15 10:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15  7:58 Getting rid of (many) dynamic link creations in the xen build Jürgen Groß
2020-10-15 10:09 ` Jan Beulich
2020-10-15 10:41   ` Jürgen Groß
2020-10-15 20:52     ` Andrew Cooper
2020-10-16  6:52       ` Jan Beulich
2020-10-16  6:58     ` Jan Beulich
2020-10-16  7:25       ` Jürgen Groß
2020-10-16  8:11         ` Jan Beulich
2020-10-15 10:49   ` Jürgen Groß [this message]
2020-10-16  6:59     ` Jan Beulich

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=0df66f1c-a02d-819c-0f05-8a7b26728e87@suse.com \
    --to=jgross@suse.com \
    --cc=George.Dunlap@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.