2008. január 22. dátummal Miklos Vajna ezt írta:
hi,
Re!
here are possible solutions:
1) do nothing and wait till somebody claims about it
2) duplicate the LICENSE, etc. files in each subpkgs (this is what
Debian does iirc)
3) create a separate -docs subpkg for these files (i think this is
Miklos Vajna wrote:
hi,
Hey :)
here is an issue: we do some automated aggregation for documentation
(README, LICENSE, AUTHORS and other files) for packages, but in case
there are subpackages, these always go to the main pkg, so there will be
even no LICENSE file in subpkgs. this may or
On Tue, Jan 22, 2008 at 05:01:55PM +0100, Gabriel C [EMAIL PROTECTED] wrote:
In fact I don't like that as well but we have to do something about.
I think we could do in fact 2 and 3 and let the developer decide in what way
he want provide the LICENSE
files for such packages. E.g: add a new
Hi devels, mom, dad...
I used to assign sec tasks to myself but after a while I realized that it
makes my work harder. I can hardly separate security related issues from
my other bugs and it's bad. I can simply keep track with sec issues thanks
to the [SEC] prefix, the assign is useless.
So
On Tue, Jan 22, 2008 at 07:22:18PM +0100, Gabriel C [EMAIL PROTECTED] wrote:
Hmm I don't really like this =)
When we want to force that then we should force for all packages.
or even that. but in that case we should decide what should be the
format.
for example we could create a collection
Miklos Vajna wrote:
On Tue, Jan 22, 2008 at 07:22:18PM +0100, Gabriel C [EMAIL PROTECTED] wrote:
Hmm I don't really like this =)
When we want to force that then we should force for all packages.
or even that. but in that case we should decide what should be the
format.
for example we
On Tue, Jan 22, 2008 at 07:45:09PM +0100, Gabriel C [EMAIL PROTECTED] wrote:
for example we could create a collection of licences, like:
/usr/share/licences/foo
/usr/share/licences/bar
Sounds logical :)
then use license=('foo') in the FrugalBuild?
I think that could work :)
hi,
something like:
- jan 24 evening: latest release bumps
- jan 25 evening: upload snapshot net,cd1-2 isos to -current-iso for
testing
- jan 26 evening: update -testing
- jan 27 evening: final upload of the release isos
- jan 29 morning: release
okay?
i expect this time a pretty smooth
