Skip to content

deckdebuild - includes target of symlinks in source - rather than the symlinks #2086

@JedMeister

Description

@JedMeister

I've just noticed that when package source includes symlinks, instead of retaining the symlinks the target of the symlink is included in the package. E.g in di-live source:

# ls -l rootfs/e2fsprogs-udeb/usr/lib/x86_64-linux-gnu/

total 484
lrwxrwxrwx 1 root root     13 Jan  3 01:41 libe2p.so.2 -> libe2p.so.2.3
-rw-r--r-- 1 root root  44720 Jan  3 01:41 libe2p.so.2.3
lrwxrwxrwx 1 root root     16 Jan  3 01:41 libext2fs.so.2 -> libext2fs.so.2.4
-rw-r--r-- 1 root root 446672 Jan  3 01:41 libext2fs.so.2.4

But in a system with di-live installed:

# ls -l /usr/lib/x86_64-linux-gnu/libe2p.so*

-rw-r--r-- 1 root root 44720 Mar  1 23:43 /usr/lib/x86_64-linux-gnu/libe2p.so.2
-rw-r--r-- 1 root root 44720 Mar  1 23:43 /usr/lib/x86_64-linux-gnu/libe2p.so.2.3

# ls -l /usr/lib/x86_64-linux-gnu/libext2fs.so*

-rw-r--r-- 1 root root 446672 Mar  1 23:43 /usr/lib/x86_64-linux-gnu/libext2fs.so.2
-rw-r--r-- 1 root root 446672 Mar  1 23:43 /usr/lib/x86_64-linux-gnu/libext2fs.so.2.4

In the case of di-live it's not really a big deal as it's only used at install time and then is removed; plus it only adds ~8kb to the size of the installed package (and less in the binary package on the mirror). But it's still worth looking into when (if!) we get a chance as perhaps it may be an issue elsewhere?

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions