You are not logged in.

#1 2018-08-18 01:16:35

adam_q
Member
Registered: 2014-09-24
Posts: 17

Any reason why we seperate lib32-* and main package PKGBUILDs?

Hi,

Recently I'm working on AUR packages like lib32-gst-plugins-ugly and lib32-gst-libav to make wine able to playback some videos.

Tons of dependency is missing and needs to be build from AUR.

I'm wondering why packages in extra/community doesn't make PKGBUILDs to create lib32-* packages at the same time?
Since we're already able to create different packages using just one PKGBUILD, and such unified packaging process would greatly improve
multilib repo.

Thanks.

Offline

#2 2018-08-18 11:40:29

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Re: Any reason why we seperate lib32-* and main package PKGBUILDs?

No package in the repositories requires  lib32-gst-plugins-ugly or lib32-gst-libav.

Offline

#3 2018-08-18 12:15:48

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,415

Re: Any reason why we seperate lib32-* and main package PKGBUILDs?

Well technically many of the formats that would make wine support of gstreamer useful do require them.

Offline

#4 2018-08-18 12:28:17

loqs
Member
Registered: 2014-03-06
Posts: 17,192

Re: Any reason why we seperate lib32-* and main package PKGBUILDs?

Makes sense that when the packages are created they would be added as optional dependencies.
I understood adam_q wanting all packages that could make lib32 versions to auto generate them leading to the i686 issue of numerous untested packages.

Offline

#5 2018-08-18 16:52:42

brebs
Member
Registered: 2007-04-03
Posts: 3,742

Re: Any reason why we seperate lib32-* and main package PKGBUILDs?

adam_q wrote:

make PKGBUILDs to create lib32-* packages at the same time?

One reason is: sometimes, the compilation options have to be different (e.g. *specifying* 32 or 64 bits, in the precise way that the particular package requires), as gotchas.

Offline

#6 2018-08-22 08:50:22

adam_q
Member
Registered: 2014-09-24
Posts: 17

Re: Any reason why we seperate lib32-* and main package PKGBUILDs?

Well, have spent over 5 hours compiling lib32-gst-plugins-bad v1.14.2 (other than the official out-of-date one),
along with lib32-gst-plugins-base-libs update to v1.14.2 (official one doesn't get updated for a long long time and maintainer isn't repsonsing at all).

The lib32-gst-plugins-bad 1.14.2 PKGBUILD can be found here:
https://gist.github.com/adam900710/a485 … abfaccd267

@loqs Yes, I'm compiling lib32-gst-* for wine. And is already maintaining lib32-gst-libav (which is relatively easy to maintain).
I'd say, it's almost flawless to maintain lib32-gst-plugins-ugly/libav, and even lib32-gst-plugins-base/good, but bad is really pain in the ass.

@brebs Indeed, for lib32-gst-plugins-bad I have to disable 3 makedepends to make life easier.
But on the other hand, for all other lib32-gst-* related packages, I don't have to bother anything other than replacing dependency with their lib32- counterpart, and add cross-compile flags.
Then call it a day.

Even for lib32-gst-plugins-bad, if all the dependency/makedepends are already here, I won't even need to modify depends at all.

I'm even considering installing an i686 arch for my wine usage, however Arch is deprecating i686.
My last hope would be buying a laptop with damn M$ windows preinstalled to just run some visual novel (and stream it back to my desktop)

I really hope Arch packager could put some priority on the lib32-* mess.

Offline

#7 2018-08-22 09:08:35

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,461

Re: Any reason why we seperate lib32-* and main package PKGBUILDs?

Arch isn't deprecating i686, it's totally gone as of 9 months ago. There's a separate distro that supports it.

lib32 is a bit of a mess because few people actually care about it.

Offline

#8 2018-08-22 09:36:00

adam_q
Member
Registered: 2014-09-24
Posts: 17

Re: Any reason why we seperate lib32-* and main package PKGBUILDs?

Well, haven't checked the status of 32bit arch for a long time.

So this also means, few people actually care about wine too?

Offline

#9 2018-08-22 11:36:00

brebs
Member
Registered: 2007-04-03
Posts: 3,742

Re: Any reason why we seperate lib32-* and main package PKGBUILDs?

No, it means that few people care about your visual novel wink

Is there a compelling requirement for lib32-gst-plugins-bad? Wine is fine without it, for most people.

If not, using the AUR is correct and appropriate.

Offline

#10 2018-08-22 15:38:26

eschwartz
Fellow
Registered: 2014-08-08
Posts: 4,097

Re: Any reason why we seperate lib32-* and main package PKGBUILDs?

Also packages in multilib cannot share the same PKGBUILD as packages in community or extra, because our dbscripts don't support split packages in different repositories.


Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

Offline

#11 2018-08-23 11:53:33

adam_q
Member
Registered: 2014-09-24
Posts: 17

Re: Any reason why we seperate lib32-* and main package PKGBUILDs?

@brebs Yeah, that's the point, visual novel is also minority.
I'd like to try archlinux32 for just for wine and VN/galgames.

Hopes KVM has working openGL support.

Offline

#12 2018-08-23 18:59:26

eschwartz
Fellow
Registered: 2014-08-08
Posts: 4,097

Re: Any reason why we seperate lib32-* and main package PKGBUILDs?

By the way I've just bumped the versions in [multilib] so this should be good now.


Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

Offline

Board footer

Powered by FluxBB