[Rpm-maint] [rpm-software-management/rpm] %defattr(644, root, root, 755) -> %_defaultdocdir gets perm 644 (#162)

2017-02-20 Thread Dominique Leuenberger
There seems to be a weird regression in rpm 4.13. If a package contains ``` %files %defattr*644,root,root,755) %doc README ``` then the file README is copied to %{_defaultdocdir}/%{name} as expected, but said directory is assigned permission 644 (instead of 755). This used to work correct

Re: [Rpm-maint] [rpm-software-management/rpm] WIP: RFC: Buildsystem overhaul (meson) (#1209)

2020-05-08 Thread Dominique Leuenberger
> @DimStar77 , > > > Just to chime in here as well: openSUSE has the 'distro bootstrap' split > > and tries to keep it under control. It's right that python3 is already in > > that chain (we build python3 is a minimal set with as few deps as possible, > > and an enhanced set, in two runs) > >

Re: [Rpm-maint] [rpm-software-management/rpm] WIP: RFC: Buildsystem overhaul (meson) (#1209)

2020-05-08 Thread Dominique Leuenberger
Just to chime in here as well: openSUSE has the 'distro bootstrap' split and tries to keep it under control. It's right that python3 is already in that chain (we build python3 is a minimal set with as few deps as possible, and an enhanced set, in two runs) I made a quick check as to what that

Re: [Rpm-maint] [rpm-software-management/rpm] WIP: RFC: Buildsystem overhaul (meson) (#1209)

2020-06-02 Thread Dominique Leuenberger
> That said, if people _really_ think Python is a problem, I'm all in favor of > CMake here. The rest of the package manager stack maintained in this > organization uses it. Heck, openSUSE's Zypper uses it! Weak argument: libzypp/zypper are not needed to bootstrap a distro (but we already have