Project

General

Profile

Actions
Copy link

Feature #16

closed

Allow customers to work with a single repo instead of multiple ones

Added by Emmanuel Jubera [SAFT] over 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Low
Assignee:
Emmanuel Jubera [SAFT]
Target version:
armel-RC 0.11.2
Start date:
05/18/2022
Due date:
% Done:

0%

Estimated time:
Affects Version/s:
armel-1.0
Fix Version/s:
Labels:

Description

The default .spec file of an application is designed to work when the sources are stored at the root of a git repository.
When the sources are located in a sub-directory of the git repo, one needs to add some linux commands in order for the build to work fine.
For example, when the sources are in a sub-directory located at the root of the git repo, the following commands added at the end of %prep section will do the trick:

mv %{_builddirsrc}/%{name}-%{version}/%{name} %{_builddirsrc}/%{name}
rm -rf %{_builddirsrc}/%{name}-%{version}
mv %{_builddirsrc}/%{name} %{_builddirsrc}/%{name}-%{version}

It would be nice to have a simpler way to specify the path to application sources.

Actions
Copy link
 #1

Updated by Yann Bodéré over 2 years ago

  • Assignee changed from Vincent Rubiolo to Marc-Antoine Riou
Actions
Copy link
 #2

Updated by Sebastien Douheret [IoT.bzh] over 2 years ago

  • Affects Version/s armel-1.0 added
Actions
Copy link
 #3

Updated by Vincent Rubiolo over 2 years ago

This is a roadmap item for customers like SAFT who develop in a single repository.

Actions
Copy link
 #4

Updated by Vincent Rubiolo about 2 years ago

  • Subject changed from Provide a simple way to specify path to sources in .spec file to Provide a simple way to specify path to source directory in .spec files
Actions
Copy link
 #5

Updated by Sebastien Douheret [IoT.bzh] about 2 years ago

  • Subject changed from Provide a simple way to specify path to source directory in .spec files to Allow customers to work with a single repo instead of multiple ones
Actions
Copy link
 #6

Updated by Marc-Antoine Riou about 2 years ago

Instead of using autosetup tool with the following args

%autosetup -p 1

Append the argument name at the end of the command

%autosetup -p 1 -n %{name}-%{version}/Common/%{name}

Then you have to be carreful about your tarball architecture, it must never change for the macro expansion to be effective

Actions
Copy link
 #7

Updated by Sebastien Douheret [IoT.bzh] almost 2 years ago

  • Status changed from New to Resolved
Actions
Copy link
 #8

Updated by Emmanuel Jubera [SAFT] almost 2 years ago

  • Assignee changed from Marc-Antoine Riou to Emmanuel Jubera [SAFT]
Actions
Copy link
 #9

Updated by Emmanuel Jubera [SAFT] almost 2 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF