Improve package.xml with large project

I am working on a large project with lot of directories
and the package.xml becomes messy:

[fileinjavascript/initialization/SystemInitialization.st[/filein]
[filein]javascript/type/Extensions.st[/filein]
...
[filein]javascript/ast/Extensions.st[/filein]
[filein]javascript/ast/JSAstNode.st[/filein]
[filein]javascript/ast/JSFunction.st[/filein]
[filein]javascript/ast/JSParenthesis.st[/filein]
[filein]javascript/ast/literals/Extensions.st[/filein]
...

I propose to add a path tag with the full path, and why not adding tag for manipulating the path
like a parentDir tag or cd tag

[path]javascript/type/[/path]
[filein]Extensions.st[/filein]
...
[path]javascript/ast/[/path]
[filein]Extensions.st[/filein]
[filein]JSAstNode.st[/filein]
[filein]JSFunction.st[/filein]
[filein]JSParenthesis.st[/filein]
[cd]literals/[/cd]
[filein]Extensions.st[/filein]
...

What's your opinion about that?

[bonzini]

Il 08/07/2012 10:45, Gwenael Casaccio ha scritto:

I am working on a large project with lot of directories
and the package.xml becomes messy:

javascript/initialization/SystemInitialization.st
javascript/type/Extensions.st
...
javascript/ast/Extensions.st
javascript/ast/JSAstNode.st
javascript/ast/JSFunction.st
javascript/ast/JSParenthesis.st
javascript/ast/literals/Extensions.st
...

I propose to add a path tag with the full path, and why not adding tag for manipulating the path
like a parentDir tag or cd tag

javascript/type/
Extensions.st
...
javascript/ast/
Extensions.st
JSAstNode.st
JSFunction.st
JSParenthesis.st
literals/
Extensions.st
...

What's your opinion about that?

Looks great. I would use a

... tag with
nested built-file, filein and file tags. It's also possible to nest the

tag. That's a bit harder to implement with the hand-rolled XML parser in kernel/, but it's really the only markup that makes some sense.

Paolo

On 08/07/2012 19:40, Paolo Bonzini wrote:

Il 08/07/2012 10:45, Gwenael Casaccio ha scritto:

I am working on a large project with lot of directories
and the package.xml becomes messy:

javascript/initialization/SystemInitialization.st
javascript/type/Extensions.st
...
javascript/ast/Extensions.st
javascript/ast/JSAstNode.st
javascript/ast/JSFunction.st
javascript/ast/JSParenthesis.st
javascript/ast/literals/Extensions.st
...

I propose to add a path tag with the full path, and why not adding tag for manipulating the path
like a parentDir tag or cd tag

javascript/type/
Extensions.st
...
javascript/ast/
Extensions.st
JSAstNode.st
JSFunction.st
JSParenthesis.st
literals/
Extensions.st
...

What's your opinion about that?
Looks great. I would use a

... tag with
nested built-file, filein and file tags. It's also possible to nest the

tag. That's a bit harder to implement with the hand-rolled XML parser in kernel/, but it's really the only markup that makes some sense.

Paolo

---

Reply to this email directly or view it on GitHub:
#6 (comment)

First step done, is something like that good enough? If yes I will
extract the args
parser in a method.

Gwen