Re: Has fedpkg + dist-git replaced rpmbuild for building new/local packages?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dne 08. 10. 19 v 11:21 Panu Matilainen napsal(a):
> On 10/8/19 11:54 AM, Dominik 'Rathann' Mierzejewski wrote:
>> On Tuesday, 08 October 2019 at 08:34, Vít Ondruch wrote:
>> [...]
>>> 2) fedpkg would not be needed if rpmbuild would be sanely able to do
>>> something like `fedpkg --release master srpm` but even so basic think
>>> requires either shuffling with files on FS or specifying million of
>>> working directories. I really don't understand why this was never
>>> improved.
>>
>> Actually, this can be improved very easy in $HOME/.rpmmacros. I use
>> this:
>> %_topdir      %(echo $HOME)/build
>> %_sourcedir   %{_topdir}/SOURCES/%{name}
>> %_specdir     %{_sourcedir}
>> %_srcrpmdir   %{_rpmdir}


We are talking about "simple" things and you suggest to start with
configuration? If that is so simple and everybody must have this, then
why is it not default?


>
> Yup. If you prefer working in a dist-git like layout, just configure
> rpm do behave that way. One possibility is simply:
>
> %_topdir    %{getenv:PWD}
> %_sourcedir    %{_topdir}
> %_specdir    %{_topdir}
> %_srcrpmdir    %{_topdir}
> %_builddir    %{_topdir}
>
> ..and perhaps %_buildrootdir as well. And then just "mkdir foo; cd
> foo" when starting a new package.
>
> The reasons that rpm doesn't default to this directory per source
> package layout include
> - there are cases where this doesn't work so well
> - it'd invalidate 20+ years of documentation on the subject
> - nobody has sat down to figure how to transition the existing
> assumptions to this type of layout without breaking everybodys setup
> in the progress


It would be nice if rpmbuild tried some small heuristic to figure out
the layout. E.g. if it fails to build SRPM because of missing sources,
try to locate the sources at current directory. This does not look that
hard. Nobody would miss the `--define "_sourcedir `pwd`"`.


Vít



>
>     - Panu -
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux