On Sun, 15 Jan 2017 15:48:10 +0000, arnaud gaboury wrote:
> OK, so I don't use %{_builddir} in my macro. So, what should I use?
Relative paths below the root of your personal build directory.
> Let's atke the first few lines:
>
> # cd %{_builddir} <-- As suggested, I don't need to cd.
> mkdir -p src/github.com/mattermost
> cd src/github.com/mattermost
> ln -s %{_builddir}/platform-master platform
>
> Here is the rpmbuild output for these lines:
> -------------------------
> + STATUS=0
> + '[' 0 -ne 0 ']'
> + cd platform-master
After this line, you are within your personal build tree below %_builddir
as set up during %prep.
To change into that build directory is an automatic step at the beginning
of every spec file section.
You've given the name of that directory as the -n option to %autopsetup or
%setup. Often, it is the root directory of the extracted source tarball.
Anything you need to set up, do it directly within that directory.
> + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
> + cd /home/makerpm/rpmbuild
> + mkdir -p src/github.com/mattermost
> + cd src/github.com/mattermost
> + ln -s /home/makerpm/rpmbuild/platform-master platform
> ----------------------------------------------------------
> May you give me the correct syntax you would use for these lines?
What's the goal of those lines? Once you've followed the symlink with "cd
platform", you're back in your original build directory.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
