Several tdemultimedia-derived packages rebuild libraries several times #200

Open
opened 3 years ago by Fat-Zer · 3 comments
Collaborator

Several tdemultimedia-derived packages rebuild libraries several times, probably it's caused by issues in upstream cmake-conversion, which was not adopted for a split-build.

Several tdemultimedia-derived packages rebuild libraries several times, probably it's caused by issues in upstream cmake-conversion, which was not adopted for a split-build.
Collaborator

I seem to recall that even the old KDE 3.5.10 autotools-based ebuilds for these packages looked messy when I dug them up to use as the basis for some of the new ebuilds. The multimedia meta-package has never been all that well-separated.

I committed whatever I could make work on the basis that a hacky-but-functional ebuild is better than no ebuild, but I really hope that someone with better skills than me can clean this up.

I seem to recall that even the old KDE 3.5.10 autotools-based ebuilds for these packages looked messy when I dug them up to use as the basis for some of the new ebuilds. The multimedia meta-package has never been all that well-separated. I committed whatever I could make work on the basis that a hacky-but-functional ebuild is better than no ebuild, but I really hope that someone with better skills than me can clean this up.
Owner

It is true that in CMake conversion there was no emphasis on split-build simply because both deb and rpm packages provide granularity at the binary package level. In order to support efforts to ensure granularity at the level of source packages, we need either pull-requests or at least reports on issues that would be good to solve.

It is true that in CMake conversion there was no emphasis on split-build simply because both deb and rpm packages provide granularity at the binary package level. In order to support efforts to ensure granularity at the level of source packages, we need either pull-requests or at least reports on issues that would be good to solve.
Collaborator

Well, kaudiocreator, kscd, and krec all overlap with each other and with libkcddb. They have to unpack each other's directories to build, and when they are built, they produce files that duplicate those the other packages may already have installed. I assume that's due to rebuilding parts of each other's code, although a lot of the files are trivial things like icons.

(The ebuilds have a list of redundant files and directories, since the only way I could find to avoid file collisions was to delete the conflicting files during the install phase.)

Well, kaudiocreator, kscd, and krec all overlap with each other and with libkcddb. They have to unpack each other's directories to build, and when they are built, they produce files that duplicate those the other packages may already have installed. I assume that's due to rebuilding parts of each other's code, although a lot of the files are trivial things like icons. (The ebuilds have a list of redundant files and directories, since the only way I could find to avoid file collisions was to delete the conflicting files during the install phase.)
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: TDE/tde-packaging-gentoo#200
Loading…
There is no content yet.