5:25 a.m.
I am writing a spec file. Everything build fine until the very last. Make
throw an error and I don't understand why.
Part of the spec file:
------------
....
cd %{_builddir}
install -Dm755 bin/platform %{buildroot}%{_datadir}/%{name}/bin/platform
install -Dm755 mattermost.sh %{buildroot}%{_bindir}/mattermost
install -Dm644 mattermost.service %{buildroot}%{_unitdir}/mattermost.service
install -Dm644 user.conf %{buildroot}%{_sysusersdir}/mattermost.conf
install -Dm644 tmpfile.conf
%{buildroot}%{_libdir}/tmpfiles.d/mattermost.conf
%files
%{_sysconfdir}/%{name}/*
%{_bindir}/%{name}
%{_unitdir}/mattermost.service
%{_sysusersdir}/mattermost.conf
%{_defaultdocdir}/*
%{_datadir}/%{name}/*
.....
---------------------------------------
Now the end of the build log:
-------------------------------
....
+ install -Dm644 user.conf
/home/makerpm/rpmbuild/BUILDROOT/mattermost-3.6-0.1.gitd64d51a.fc25.x86_64/usr/lib/sysusers.d/mattermost.conf
+ install -Dm644 tmpfile.conf
/home/makerpm/rpmbuild/BUILDROOT/mattermost-3.6-0.1.gitd64d51a.fc25.x86_64/usr/lib64/tmpfiles.d/mattermost.conf
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/brp-compress
+ /usr/lib/rpm/brp-strip /usr/bin/strip
+ /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump
+ /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1
+ /usr/lib/rpm/brp-python-hardlink
+ /usr/lib/rpm/redhat/brp-java-repack-jars
error: Bad file:
/home/makerpm/build_package/mattermost/mattermost-user.conf: No such file
or directory
----------------------------------------
build directory:
[makerpm@thetradinghall mattermost]$ ls -al
total 30580
drwxrwxr-x 1 makerpm makerpm 346 Jan 14 11:50 .
drwxrwxr-x 1 makerpm makerpm 58 Jan 13 16:50 ..
drwxr-xr-x 1 makerpm makerpm 26 Jan 13 16:21 bin
-rw-rw-r-- 1 makerpm makerpm 156500 Jan 14 11:43
.build-3.6-0.1.gitd64d51a.fc25.log
-rw-rw-r-- 1 makerpm makerpm 104 Jan 13 10:17 .gitignore
-rw-rw-r-- 1 makerpm makerpm 31108310 Jan 13 16:07 master.zip
-rw-rw-r-- 1 makerpm makerpm 319 Jan 13 10:17 mattermost.service
-rw-rw-r-- 1 makerpm makerpm 169 Jan 13 10:17 mattermost.sh
-rw-rw-r-- 1 makerpm makerpm 4031 Jan 14 11:38 mattermost.spec
-rw-r--r-- 1 makerpm makerpm 16384 Jan 14 11:50 .mattermost.spec.swp
drwxr-xr-x 1 makerpm makerpm 22 Jan 13 16:21 pkg
drwxr-xr-x 1 makerpm makerpm 596 Jan 14 11:42 platform-master
drwxr-xr-x 1 makerpm makerpm 20 Jan 13 16:07 src
-rw-rw-r-- 1 makerpm makerpm 1169 Jan 13 10:17 .SRCINFO
-rw-rw-r-- 1 makerpm makerpm 164 Jan 13 10:17 tmpfile.conf
-rw-rw-r-- 1 makerpm makerpm 32 Jan 13 10:17 user.conf
------------------------------
I don't understand why the mattermost-user.conf file comes in the build
process. There is no place where this file can be found, and no
instructions in the spec file regarding this file.
The log doesn't say much. How can I solve this issue? Is there any method,
hint?
Thank you for help.
10:16 a.m.
On Sat, 14 Jan 2017 11:25:07 +0000, arnaud gaboury wrote:
+ /usr/lib/rpm/brp-python-hardlink
+ /usr/lib/rpm/redhat/brp-java-repack-jars
error: Bad file:
/home/makerpm/build_package/mattermost/mattermost-user.conf: No such file
or directory
You've not given enough information, unfortunately. Does the output end
there? If so, it has not reached the %files processing section it seems.
Uploading the full spec file or even the src.rpm would have been a great
idea.
Tell a bit about the "build_package" directory below $HOME.
/home/makerpm is the home of your user. /home/makerpm/rpmbuild is
the home of rpmbuild related files. What is the "build_package" dir?
How do you use that dir? Maybe you've added that dir to some RPM macros?
10:57 a.m.
On Sat, Jan 14, 2017 at 5:17 PM Michael Schwendt <mschwendt(a)gmail.com>
wrote:
%prep
%autosetup -n platform-master
# many golang binaries are "vendoring" (bundling) sources, so remove them.
Those dependencies need to be packaged independently.
cd %{_builddir}
mkdir -p src/github.com/mattermost
cd src/github.com/mattermost
ln -s %{_builddir}/platform-master platform
# build only for 64 bits
cd platform
sed -n '1,/cp README.md/p;/^run-server:/,$p' -i Makefile
sed -r -i Makefile \
-e 's/^package: build build-client/package: build-linux build-client/' \
-e 's/GOARCH=amd64//' \
-e 's/^BUILD_HASH =.*/BUILD_HASH = none/'
sed -i webapp/Makefile \
-e '/npm install/a \ rm
node_modules/pngquant-bin/vendor/pngquant\n ln -s /usr/bin/pngquant
node_modules/pngquant-bin/vendor/pngquant'
%build
cd %{_builddir}/src/github.com/mattermost/platform
GOPATH=%{_builddir} BUILD_NUMBER=%{version}-%{release} make %{?_smp_mflags}
package
%install
cd %{_builddir}/src/github.com/mattermost/platform
rm -rf %{buildroot}
install -dm755 %{buildroot}%{_datadir}/webapps \
%{buildroot}/var/log/%{name} \
%{buildroot}%{_sysconfdir}/webapps \
%{buildroot}%{_datadir}/{licenses,doc}/%{name}
cp -a dist/mattermost %{buildroot}%{_datadir}/webapps/%{name}
cd %{buildroot}%{_datadir}/webapps/%{name}
rm -rf logs
ln -s /var/log/%{name} logs
mkdir -p %{buildroot}%{_sysconfdir}/webapps/%{name}
mv config/config.json %{buildroot}%{_sysconfdir}/webapps/%{name}
ln -s %{_sysconfdir}/webapps/%{name} config
sed -e 's@"Directory": ".*"@"Directory":
"/var/lib/mattermost/"@g' \
-e 's@tcp(dockerhost:3306)@unix(/run/mysqld/mysqld.sock)@g' \
-i %{buildroot}%{_sysconfdir}/webapps/%{name}/config.json
mv NOTICE.txt README.md %{buildroot}%{_defaultdocdir}/%{name}
cd %{_builddir}
install -Dm755 bin/platform
%{buildroot}%{_datadir}/webapps/%{name}/bin/platform
install -Dm755 mattermost.sh %{buildroot}%{_bindir}/mattermost
install -Dm644 mattermost.service %{buildroot}%{_unitdir}/mattermost.service
install -Dm644 user.conf %{buildroot}%{_sysusersdir}/mattermost.conf
%files
%{_sysconfdir}/webapps/%{name}/*
%{_bindir}/%{name}
%{_unitdir}/mattermost.service
%{_sysusersdir}/mattermost.conf
%{_defaultdocdir}/*
%{_datadir}/webapps/%{name}/*
%post
systemd-sysusers mattermost.conf
if [[ ! -e var/lib/mattermost ]]; then
install -dm700 -o mattermost var/lib/mattermost
fi
On Sat, 14 Jan 2017 11:25:07 +0000, arnaud gaboury wrote:
> + /usr/lib/rpm/brp-python-hardlink
> + /usr/lib/rpm/redhat/brp-java-repack-jars
> error: Bad file:
> /home/makerpm/build_package/mattermost/mattermost-user.conf: No such file
> or directory
You've not given enough information, unfortunately. Does the output end
there?
YES
If so, it has not reached the %files processing section it seems.
Uploading the full spec file or even the src.rpm would have been a
great
idea.
Here it goes:
a bit about the "build_package" directory below $HOME.
/home/makerpm is the home of your user. /home/makerpm/rpmbuild is
the home of rpmbuild related files. What is the "build_package" dir?
I followed this wiki[0], section First steps.
mkdir ~/build_package/mattermost (in wiki is equivalent to
~/packaging-work/howdy).
I will have a closest look as it seems this issue may comes from here. In
my spec there seems to be a confusion between %{_builddir} and
~/build_package/mattermost . There are the same when they shouldn't. It
seems I have built with TWO build dir!
Thank you for this remark . I will change and build with only one build
directory
How do you use that dir? Maybe you've added that dir to some RPM
macros?
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
12:53 p.m.
On Sat, Jan 14, 2017 at 5:57 PM arnaud gaboury <arnaud.gaboury(a)gmail.com>
wrote:
On Sat, Jan 14, 2017 at 5:17 PM Michael Schwendt
<mschwendt(a)gmail.com>
wrote:
On Sat, 14 Jan 2017 11:25:07 +0000, arnaud gaboury wrote:
> + /usr/lib/rpm/brp-python-hardlink
> + /usr/lib/rpm/redhat/brp-java-repack-jars
> error: Bad file:
> /home/makerpm/build_package/mattermost/mattermost-user.conf: No such file
> or directory
You've not given enough information, unfortunately. Does the output end
there?
YES
If so, it has not reached the %files processing section it seems.
Uploading the full spec file or even the src.rpm would have been a great
idea.
Here it goes:
%prep
%autosetup -n platform-master
# many golang binaries are "vendoring" (bundling) sources, so remove them.
Those dependencies need to be packaged independently.
cd %{_builddir}
mkdir -p src/github.com/mattermost
cd src/github.com/mattermost
ln -s %{_builddir}/platform-master platform
# build only for 64 bits
cd platform
sed -n '1,/cp README.md/p;/^run-server:/,$p' -i Makefile
sed -r -i Makefile \
-e 's/^package: build build-client/package: build-linux build-client/'
\
-e 's/GOARCH=amd64//' \
-e 's/^BUILD_HASH =.*/BUILD_HASH = none/'
sed -i webapp/Makefile \
-e '/npm install/a \ rm
node_modules/pngquant-bin/vendor/pngquant\n ln -s /usr/bin/pngquant
node_modules/pngquant-bin/vendor/pngquant'
%build
cd %{_builddir}/src/github.com/mattermost/platform
GOPATH=%{_builddir} BUILD_NUMBER=%{version}-%{release} make
%{?_smp_mflags} package
%install
cd %{_builddir}/src/github.com/mattermost/platform
rm -rf %{buildroot}
install -dm755 %{buildroot}%{_datadir}/webapps \
%{buildroot}/var/log/%{name} \
%{buildroot}%{_sysconfdir}/webapps \
%{buildroot}%{_datadir}/{licenses,doc}/%{name}
cp -a dist/mattermost %{buildroot}%{_datadir}/webapps/%{name}
cd %{buildroot}%{_datadir}/webapps/%{name}
rm -rf logs
ln -s /var/log/%{name} logs
mkdir -p %{buildroot}%{_sysconfdir}/webapps/%{name}
mv config/config.json %{buildroot}%{_sysconfdir}/webapps/%{name}
ln -s %{_sysconfdir}/webapps/%{name} config
sed -e 's@"Directory": ".*"@"Directory":
"/var/lib/mattermost/"@g' \
-e 's@tcp(dockerhost:3306)@unix(/run/mysqld/mysqld.sock)@g' \
-i %{buildroot}%{_sysconfdir}/webapps/%{name}/config.json
mv NOTICE.txt README.md %{buildroot}%{_defaultdocdir}/%{name}
cd %{_builddir}
install -Dm755 bin/platform
%{buildroot}%{_datadir}/webapps/%{name}/bin/platform
install -Dm755 mattermost.sh %{buildroot}%{_bindir}/mattermost
install -Dm644 mattermost.service
%{buildroot}%{_unitdir}/mattermost.service
install -Dm644 user.conf %{buildroot}%{_sysusersdir}/mattermost.conf
%files
%{_sysconfdir}/webapps/%{name}/*
%{_bindir}/%{name}
%{_unitdir}/mattermost.service
%{_sysusersdir}/mattermost.conf
%{_defaultdocdir}/*
%{_datadir}/webapps/%{name}/*
%post
systemd-sysusers mattermost.conf
if [[ ! -e var/lib/mattermost ]]; then
install -dm700 -o mattermost var/lib/mattermost
fi
a bit about the "build_package" directory below $HOME.
/home/makerpm is the home of your user. /home/makerpm/rpmbuild is
the home of rpmbuild related files. What is the "build_package" dir?
I followed this wiki[0], section First steps.
mkdir ~/build_package/mattermost (in wiki is equivalent to
~/packaging-work/howdy).
I will have a closest look as it seems this issue may comes from here. In
my spec there seems to be a confusion between %{_builddir} and
~/build_package/mattermost . There are the same when they shouldn't. It
seems I have built with TWO build dir!
Thank you for this remark . I will change and build with only one build
directory
In fact, I realize I am totally confused between the "old" method I used to
build .rpm and this new wiki using fedpkg. Before, I used to have BUILD,
BUILDROOT, SOURCES etc folders inside rpmbuild. Now, I am not sure how to
setup my build directory.
How do you use that dir? Maybe you've added that dir to some RPM
macros?
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
1:28 p.m.
On Sat, Jan 14, 2017 at 7:53 PM arnaud gaboury <arnaud.gaboury(a)gmail.com>
wrote:
On Sat, Jan 14, 2017 at 5:57 PM arnaud gaboury
<arnaud.gaboury(a)gmail.com>
wrote:
On Sat, Jan 14, 2017 at 5:17 PM Michael Schwendt <mschwendt(a)gmail.com>
wrote:
On Sat, 14 Jan 2017 11:25:07 +0000, arnaud gaboury wrote:
> + /usr/lib/rpm/brp-python-hardlink
> + /usr/lib/rpm/redhat/brp-java-repack-jars
> error: Bad file:
> /home/makerpm/build_package/mattermost/mattermost-user.conf: No such file
> or directory
You've not given enough information, unfortunately. Does the output end
there?
YES
If so, it has not reached the %files processing section it seems.
Uploading the full spec file or even the src.rpm would have been a great
idea.
Here it goes:
%prep
%autosetup -n platform-master
# many golang binaries are "vendoring" (bundling) sources, so remove them.
Those dependencies need to be packaged independently.
cd %{_builddir}
mkdir -p src/github.com/mattermost
cd src/github.com/mattermost
ln -s %{_builddir}/platform-master platform
# build only for 64 bits
cd platform
sed -n '1,/cp README.md/p;/^run-server:/,$p' -i Makefile
sed -r -i Makefile \
-e 's/^package: build build-client/package: build-linux build-client/'
\
-e 's/GOARCH=amd64//' \
-e 's/^BUILD_HASH =.*/BUILD_HASH = none/'
sed -i webapp/Makefile \
-e '/npm install/a \ rm
node_modules/pngquant-bin/vendor/pngquant\n ln -s /usr/bin/pngquant
node_modules/pngquant-bin/vendor/pngquant'
%build
cd %{_builddir}/src/github.com/mattermost/platform
GOPATH=%{_builddir} BUILD_NUMBER=%{version}-%{release} make
%{?_smp_mflags} package
%install
cd %{_builddir}/src/github.com/mattermost/platform
rm -rf %{buildroot}
install -dm755 %{buildroot}%{_datadir}/webapps \
%{buildroot}/var/log/%{name} \
%{buildroot}%{_sysconfdir}/webapps \
%{buildroot}%{_datadir}/{licenses,doc}/%{name}
cp -a dist/mattermost %{buildroot}%{_datadir}/webapps/%{name}
cd %{buildroot}%{_datadir}/webapps/%{name}
rm -rf logs
ln -s /var/log/%{name} logs
mkdir -p %{buildroot}%{_sysconfdir}/webapps/%{name}
mv config/config.json %{buildroot}%{_sysconfdir}/webapps/%{name}
ln -s %{_sysconfdir}/webapps/%{name} config
sed -e 's@"Directory": ".*"@"Directory":
"/var/lib/mattermost/"@g' \
-e 's@tcp(dockerhost:3306)@unix(/run/mysqld/mysqld.sock)@g' \
-i %{buildroot}%{_sysconfdir}/webapps/%{name}/config.json
mv NOTICE.txt README.md %{buildroot}%{_defaultdocdir}/%{name}
cd %{_builddir}
install -Dm755 bin/platform
%{buildroot}%{_datadir}/webapps/%{name}/bin/platform
install -Dm755 mattermost.sh %{buildroot}%{_bindir}/mattermost
install -Dm644 mattermost.service
%{buildroot}%{_unitdir}/mattermost.service
install -Dm644 user.conf %{buildroot}%{_sysusersdir}/mattermost.conf
%files
%{_sysconfdir}/webapps/%{name}/*
%{_bindir}/%{name}
%{_unitdir}/mattermost.service
%{_sysusersdir}/mattermost.conf
%{_defaultdocdir}/*
%{_datadir}/webapps/%{name}/*
%post
systemd-sysusers mattermost.conf
if [[ ! -e var/lib/mattermost ]]; then
install -dm700 -o mattermost var/lib/mattermost
fi
a bit about the "build_package" directory below $HOME.
/home/makerpm is the home of your user. /home/makerpm/rpmbuild is
the home of rpmbuild related files. What is the "build_package" dir?
I followed this wiki[0], section First steps.
mkdir ~/build_package/mattermost (in wiki is equivalent to
~/packaging-work/howdy).
I will have a closest look as it seems this issue may comes from here. In
my spec there seems to be a confusion between %{_builddir} and
~/build_package/mattermost . There are the same when they shouldn't. It
seems I have built with TWO build dir!
Thank you for this remark . I will change and build with only one build
directory
In fact, I realize I am totally confused between the "old" method I used
to build .rpm and this new wiki using fedpkg. Before, I used to have BUILD,
BUILDROOT, SOURCES etc folders inside rpmbuild. Now, I am not sure how to
setup my build directory.
Issue solved. As most often, it was an obvious issue: one of my Source file
had a wrong name: mattermost-user.conf, instead of user.conf
Build is now successful.
How do you use that dir? Maybe you've added that dir to some RPM macros?
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
5:25 p.m.
On Sat, 14 Jan 2017 18:53:30 +0000, arnaud gaboury wrote:
In fact, I realize I am totally confused between the "old"
method I used to
build .rpm and this new wiki using fedpkg. Before, I used to have BUILD,
BUILDROOT, SOURCES etc folders inside rpmbuild. Now, I am not sure how to
setup my build directory.
There is the default ~/rpmbuild tree, which you can continue to use.
src.rpm packages extracted with rpmbuild end up in that tree.
Many packagers create an own ~/.rpmmacros however in order to
adjust the directory layout of the rpmbuild tree.
5:21 p.m.
On Sat, 14 Jan 2017 16:57:42 +0000, arnaud gaboury wrote:
%prep
%autosetup -n platform-master
# many golang binaries are "vendoring" (bundling) sources, so remove them.
Those dependencies need to be packaged independently.
cd %{_builddir}
Don't get accustomed to that. Don't cd into %_builddir directly.
Run "rpm -E %_builddir" to see which directory that macro expands to.
There are corner-cases when you need to use the %_builddir macro.
In most cases, you don't need to use it at all.
The %setup and %autosetup macros define the top-level build directory
below %_builddir, and at the start of every spec file section (e.g. %build,
%install, %check, even %files), that build directory is entered automatically.
It may also be cleaned up automatically depending on your rpmbuild option
and the default %clean section.
Create all your other working directories below $(pwd), not anywhere
above %_builddir. You can access relative paths from current
directory, which is much more convenient.
In your case, because of using %autosetup -n platform-master, the
root directory is
%{_builddir}/platform-master
and if you read rpmbuild output, you should see that the directory is
entered automatically for every spec file section. If you've used %autosetup
correctly, you should find the extracted source code below that directory,
too. If you need another top-level directory, you can use option -c to
create it.
The way you jump to absolute paths and even create links that lead back to
some absolute %_builddir path makes the spec file look like a mess.
8:55 a.m.
On Sun, Jan 15, 2017 at 12:22 AM Michael Schwendt <mschwendt(a)gmail.com>
wrote:
On Sat, 14 Jan 2017 16:57:42 +0000, arnaud gaboury wrote:
> %prep
> %autosetup -n platform-master
>
> # many golang binaries are "vendoring" (bundling) sources, so remove
them.
> Those dependencies need to be packaged independently.
> cd %{_builddir}
Don't get accustomed to that. Don't cd into %_builddir directly.
Run "rpm -E %_builddir" to see which directory that macro expands to.
There are corner-cases when you need to use the %_builddir macro.
In most cases, you don't need to use it at all.
The %setup and %autosetup macros define the top-level build directory
below %_builddir, and at the start of every spec file section (e.g. %build,
%install, %check, even %files), that build directory is entered
automatically.
It may also be cleaned up automatically depending on your rpmbuild option
and the default %clean section.
Create all your other working directories below $(pwd), not anywhere
above %_builddir. You can access relative paths from current
directory, which is much more convenient.
In your case, because of using %autosetup -n platform-master, the
root directory is
%{_builddir}/platform-master
and if you read rpmbuild output, you should see that the directory is
entered automatically for every spec file section. If you've used
%autosetup
correctly, you should find the extracted source code below that directory,
too. If you need another top-level directory, you can use option -c to
create it.
The way you jump to absolute paths and even create links that lead back to
some absolute %_builddir path makes the spec file look like a mess.
Thank you so much for all these good practices. These kinds of hints are
very hard to find in fact. It is easy to quickly mess everything when it
comes to using macros.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
9:48 a.m.
On Sun, Jan 15, 2017 at 12:22 AM Michael Schwendt <mschwendt(a)gmail.com>
wrote:
On Sat, 14 Jan 2017 16:57:42 +0000, arnaud gaboury wrote:
> %prep
> %autosetup -n platform-master
>
> # many golang binaries are "vendoring" (bundling) sources, so remove
them.
> Those dependencies need to be packaged independently.
> cd %{_builddir}
Don't get accustomed to that. Don't cd into %_builddir directly.
Run "rpm -E %_builddir" to see which directory that macro expands to.
There are corner-cases when you need to use the %_builddir macro.
In most cases, you don't need to use it at all.
OK, so I don't use %{_builddir} in my macro. So, what should I use?
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
+ /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?
The %setup and %autosetup macros define the top-level build directory
below %_builddir, and at the start of every spec file section (e.g. %build,
%install, %check, even %files), that build directory is entered
automatically.
It may also be cleaned up automatically depending on your rpmbuild option
and the default %clean section.
Create all your other working directories below $(pwd), not anywhere
above %_builddir. You can access relative paths from current
directory, which is much more convenient.
In your case, because of using %autosetup -n platform-master, the
root directory is
%{_builddir}/platform-master
and if you read rpmbuild output, you should see that the directory is
entered automatically for every spec file section. If you've used
%autosetup
correctly, you should find the extracted source code below that directory,
too. If you need another top-level directory, you can use option -c to
create it.
The way you jump to absolute paths and even create links that lead back to
some absolute %_builddir path makes the spec file look like a mess.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
1:15 p.m.
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.
2657
days inactive
2658
days old
9 comments
2 participants
participants (2)
-
arnaud gaboury -
Michael Schwendt