-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> One issue I can't really figure out is the very different naming all the
> distributions use for the different packages, even core packages. RPM
> also can specify a dependency on files (like "/bin/sh has to be
> present"). Your thoughs on this
Joerg Hohwiller wrote:
Hi there,
[cut.]
That was one of the first things I wanted to implement in the plugin but
I've done many rounds of design on it and it is finally done:
To summarize:
src/main/unix/files goes in all packages, all formats
src/main/unix/files-rpm goes in all packages,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
> [cut.]
> That was one of the first things I wanted to implement in the plugin but
> I've done many rounds of design on it and it is finally done:
>
> To summarize:
>
> src/main/unix/files goes in all packages, all formats
> src/main/unix
Joerg Hohwiller wrote:
> Hi Trygve,
>
> thanks for your reply. Now worries for the delay.
> Usually I am the one who gets lost for a long time...
>
Mainly because those utils one or more of 1) buggy, 2) slow, 3)
incomplete and 4) not sufficient.
>>> I see that problem but do NOT agree w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Trygve,
thanks for your reply. Now worries for the delay.
Usually I am the one who gets lost for a long time...
>>> Mainly because those utils one or more of 1) buggy, 2) slow, 3)
>>> incomplete and 4) not sufficient.
>>
>> I see that problem but
Joerg Hohwiller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mainly because those utils one or more of 1) buggy, 2) slow, 3)
incomplete and 4) not sufficient.
I see that problem but do NOT agree with the general argument.
1) we are a community and progress is made
2) not very importa
Trygve Laugstøl wrote
> Have you looked at the other RPM plugin? It seems that Brett Okken is putting
> a lot of effort into it.
Not yet. Hopefully some weekend down the road.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Mainly because those utils one or more of 1) buggy, 2) slow, 3)
> incomplete and 4) not sufficient.
I see that problem but do NOT agree with the general argument.
1) we are a community and progress is made
2) not very important to me
3) see 1)
4) i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Lee,
>
> **Joerg Hohwiller wrote:
> **> I mean there is maven-dependency-plugin,
>> maven-resource-plugin and filtering
>> and all what maven already offers.
>> Why not just let the user build the package
>> content with all features of maven
>>
Lee Thompson wrote:
**Joerg Hohwiller wrote:
**> I mean there is maven-dependency-plugin,
> maven-resource-plugin and filtering
> and all what maven already offers.
> Why not just let the user build the package
> content with all features of maven
> to build.outputDirectory and then build
Joerg Hohwiller wrote:
> I mean there is maven-dependency-plugin,
> maven-resource-plugin and filtering
> and all what maven already offers.
> Why not just let the user build the package
> content with all features of maven
> to build.outputDirectory and then build
> a package from that.
rpm-c
Joerg Hohwiller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Trygve, hi everybody,
I started to get into unix-maven-plugin.
So far I like the general configuration of
common package meta-data and your excellent
documentation how this is mapped down according
to the actual format.
Ho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Trygve, hi everybody,
I started to get into unix-maven-plugin.
So far I like the general configuration of
common package meta-data and your excellent
documentation how this is mapped down according
to the actual format.
However currently the site
13 matches
Mail list logo
