Just made grep across all Fedora spec files
```console
[tkloczko@pers-jacek SPECS.fedora]$ grep SPECPARTS *
python-bidict.spec:# SPECPARTS dir in %%_builddir/%%buildsubdir is leaking to
setuptools package
python-bidict.spec:rm -rf SPECPARTS
python-cairocffi.spec:- Drop rmdir SPECPARTS
python-chaospy.spec:rm -rf SPECPARTS
python-linkify-it-py.spec:- Stop removing the SPECPARTS directory, it doesn't
exist
python-linkify-it-py.spec:- Remove empty SPECPARTS directory that breaks build
python-mechanize.spec:rm -rf SPECPARTS
python-neo.spec:# remove rpm's SPECPARTS file
python-neo.spec:rm -rf SPECPARTS
python-nihtest.spec:# Work around issue with package discovery due to SPECPARTS
dir
python-nose2.spec:rm -rf SPECPARTS
python-numpoly.spec:rm -rf SPECPARTS
python-quantities.spec:# Work around confusion with SPECPARTS directory looking
like a package to
python-quantities.spec:rm -rf SPECPARTS
python-uc-micro-py.spec:rm -rf SPECPARTS
qcad.spec:rm -rf ../*-SPECPARTS
rpm.spec:- Use mkdir -p for creating SPECPARTS dir
traceroute.spec:%make_build CFLAGS="$RPM_OPT_FLAGS" LDFLAGS="$RPM_LD_FLAGS"
SKIPDIRS="${RPM_SPECPARTS_DIR##*/}"
```
Few of those cases already have been sorted out by source tree maintainers.
Another question is .. is it really worth to keep SPECPARTS extension in rpm? 🤔
So far not been able to find even SINGLE case of use that.
IMO that whole SPECPARTS created so far more issues (and by this wasted more
man/hours) than saved any time on packaging.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2885#issuecomment-1927384811
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2885/c1927384...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
