On Tue, Feb 17, 2015 at 09:10:09AM +0100, Markus Niebel wrote:
Am 11.02.2015 um 14:02 schrieb Michael Olbrich:
On Wed, Feb 11, 2015 at 12:19:34PM +0100, Juergen Borleis wrote:
On Wednesday 11 February 2015 11:50:16 Hubert Feurstein wrote:
IMHO the proposal by Markus makes sense. I have had
Hello,
Am 11.02.2015 um 14:02 schrieb Michael Olbrich:
Hi,
On Wed, Feb 11, 2015 at 12:19:34PM +0100, Juergen Borleis wrote:
On Wednesday 11 February 2015 11:50:16 Hubert Feurstein wrote:
IMHO the proposal by Markus makes sense. I have had the same issues
with collecting license texts in the
Hi,
On Thu, Feb 12, 2015 at 08:33:32AM +0100, Markus Niebel wrote:
On Wednesday 11 February 2015 11:50:16 Hubert Feurstein wrote:
IMHO the proposal by Markus makes sense. I have had the same issues
with collecting license texts in the past. So a solution integrated in
PTXdist would be
Hi,
On Wednesday 11 February 2015 11:50:16 Hubert Feurstein wrote:
IMHO the proposal by Markus makes sense. I have had the same issues
with collecting license texts in the past. So a solution integrated in
PTXdist would be great. Because then it would be possible to collect
the license texts
Hello,
IMHO the proposal by Markus makes sense. I have had the same issues
with collecting license texts in the past. So a solution integrated in
PTXdist would be great. Because then it would be possible to collect
the license texts depending on the config options of a package
(sometimes plugins
Hi,
On Wed, Feb 11, 2015 at 12:19:34PM +0100, Juergen Borleis wrote:
On Wednesday 11 February 2015 11:50:16 Hubert Feurstein wrote:
IMHO the proposal by Markus makes sense. I have had the same issues
with collecting license texts in the past. So a solution integrated in
PTXdist would be
Hello Juergen,
Am 11.02.2015 um 12:19 schrieb Juergen Borleis:
Hi,
On Wednesday 11 February 2015 11:50:16 Hubert Feurstein wrote:
IMHO the proposal by Markus makes sense. I have had the same issues
with collecting license texts in the past. So a solution integrated in
PTXdist would be
Hello Markus,
I'm no expert at this topic but here is how I would handle this:
1. Collect all existing files in state/pkg.license into a license
list. Example:
#!/bin/sh
if [ $# -eq 0 -o ! -e $1/state ]; then
echo usage: $0 ptxdist_platform_dir
exit 1
fi
for file in $1/state/*.license
Hi,
If I understand correctly the auditing procedure before this patch would be:
1. Collect all existing files in state/pkg.license
2. Each .license file contains the license name (e.g. GPL) -- use
this to find the actual license text
3. Audit each license
What would be the difference after
Hello,
Am 29.01.2015 um 21:23 schrieb Guillermo Rodriguez Garcia:
Hi,
If I understand correctly the auditing procedure before this patch would be:
1. Collect all existing files in state/pkg.license
2. Each .license file contains the license name (e.g. GPL) -- use
this to find the actual
From: Markus Niebel markus.nie...@tq-group.com
just as an RFC: it would be good to have above said features to ease
deployment and auditing.
First patch implements this feature as an addon of the targetinstall
stage. Second patch shows the feature for a package that uses it's own
license
TODO:
11 matches
Mail list logo
