On Mon, Jul 09, 2012 at 04:17:27PM +0300, Elan Ruusamäe wrote:
On 09.07.2012 15:40, Kacper Kornet wrote:
those (except pldnotify.awk and pearize.sh) are daily tools used to
manage pld packages developing
do they all fit to rpm-build-tools git repo? can those be imported
with full cvs
On Wed, Jul 11, 2012 at 03:03:44PM +0200, Kacper Kornet wrote:
A small doubt about it. Package rpm-build-tools is cloned to chroots
used by builders. Are all this tools really needed there?
If they do not pull further dependencies, they won't hurt.
Greets,
Jacek
On Wed, Jul 11, 2012 at 03:09:26PM +0200, Jacek Konieczny wrote:
On Wed, Jul 11, 2012 at 03:03:44PM +0200, Kacper Kornet wrote:
A small doubt about it. Package rpm-build-tools is cloned to chroots
used by builders. Are all this tools really needed there?
If they do not pull further
On 11.07.2012 16:03, Kacper Kornet wrote:
A small doubt about it. Package rpm-build-tools is cloned to chroots
used by builders. Are all this tools really needed there?
in src-builders probably (two setups both on ep09), but in bin-builder,
only builder script is needed, which i have symlink
On 11.07.2012 17:08, Elan Ruusamäe wrote:
On 11.07.2012 16:03, Kacper Kornet wrote:
A small doubt about it. Package rpm-build-tools is cloned to chroots
used by builders. Are all this tools really needed there?
in src-builders probably (two setups both on ep09), but in
bin-builder, only
On Wed, Jul 11, 2012 at 05:08:40PM +0300, Elan Ruusamäe wrote:
On 11.07.2012 16:03, Kacper Kornet wrote:
A small doubt about it. Package rpm-build-tools is cloned to
chroots used by builders. Are all this tools really needed there?
in src-builders probably (two setups both on ep09), but in
On Wed, Jul 11, 2012 at 04:21:46PM +0200, Kacper Kornet wrote:
On Wed, Jul 11, 2012 at 05:08:40PM +0300, Elan Ruusamäe wrote:
On 11.07.2012 16:03, Kacper Kornet wrote:
A small doubt about it. Package rpm-build-tools is cloned to
chroots used by builders. Are all this tools really needed
On 11.07.2012 17:26, Kacper Kornet wrote:
In src builders I prefer to keep it in clone of git repo. This way if I
want to make a final check if the new changes don't break anything I
don't need to produce rpm, upgrade it and in case of breakage downgrade.
One more idea. The history of
On 09.07.2012 08:49, Jan Rękorajski wrote:
There were some scripts and other files directly under packages/ :
adapter
adapter.awk
bconds.txt
builder
check-unused-files.py
ci
civim
clean-distfiles.sh
compile.sh
COPYING
dropin
fetchsrc_request
get-all-specs.sh
kde4brs.sh
kde4devel2head.sh
On Mon, Jul 09, 2012 at 03:21:29PM +0300, Elan Ruusamäe wrote:
On 09.07.2012 08:49, Jan Rękorajski wrote:
There were some scripts and other files directly under packages/ :
adapter
adapter.awk
bconds.txt
builder
check-unused-files.py
ci
civim
clean-distfiles.sh
compile.sh
COPYING
On 09.07.2012 15:40, Kacper Kornet wrote:
those (except pldnotify.awk and pearize.sh) are daily tools used to
manage pld packages developing
do they all fit to rpm-build-tools git repo? can those be imported
with full cvs history?
Yes, they can be imported with cvs history if we only
11 matches
Mail list logo
