Il Mercoledì 26 Marzo 2014 10:07, Denis Laxalde <de...@laxalde.org> ha scritto:
Hi,
>Andrea Palazzi a écrit :
>> So, the package is good, the only thing that should be changed, if we
>> want to upload the package as soon as possible, is that with this
>> packaging, code-aster-mpi-engine should depend on code-aster and not
>> vice-versa.
>
>I don't understand why we'd want this. With the current binary layout,
>code-aster (the Python library and elements catalog) cannot be used
>without an engine (the aster binary), whereas the engine could (in
>theory) be used without the code-aster Python library or elements
>catalog (although it wouldn't be more useful than a python interpreter).
>
From the Debian policy: "The Depends field should be used if the depended-on
package is
required for the depending package to provide a significant amount of
functionality."
So I would say that code-aster-engine depends on
code-aster. On the other hand also code-aster depends on engine, which
makes it a circular dependency. They are not forbidden and we can live
with it, however I would like to avoid it if possible.
Note also that as_run (code-aster-run) depends on code-aster because of
config.txt so we would have another circular dependency... the more I think
about it the more I feel like we have to find a good solution for this.
> Note however that code-aster-run puts some files under
>> /usr/lib/codeaster, so we shoult ideally take also care of
>> code-aster-run and code-aster-gui packages.
>
>This symlink is precisely here so that as_run (from code-aster-run
>package) can still be used when aster is installed in /usr/lib/aster
>(not /usr/lib/codeaster). Ultimately, astk's packaging should be updated
>in order not to need this, but I currently I no time to do this.
Ok, let's just keep it as it is then.
> - In the process, I'd like also to switch from svn to git.
>Not sure I get your point. It's already done.
I was talking about the astk packages, but if you don't have the time to
maintain them then let's stay on svn.
>> - as_run doesn't work out of the box: it relies on having informations
>> about available versions in the file /etc/codeaster/aster ; the script
>> update-codeaster-engines takes care of this, it should be run on
>> postinst/postrm scripts of the code-aster-*-engine packages.
>
>What does not work? AFAICT, it works: I can run 'as_run xxx.export' or
>some tests like 'as_run --test mtlp100a'.
>
You're right: it works because the template /etc/codeaster/aster file points to
STABLE when installed.
However a sysadmin is not supposed to edit the file every time an engine
package is installed or removed: as I said previously, this is more a status
file than a config file, so the issue is still valid: we need a way to update
the /etc/codeaster/aster file when an engine package is installed, be it the
old postinst scripts or some other mechanism.
>> - provide also the serial version
>>
>>- a simple script to run the test cases would be nice... the .comm file
>>that was used for this purpose has been removed from upstream, or it's
>>just me that can't find it?
In the previous packaging there were an as_test script, maybe I can work on
it...
>> - 11.5 is already out
> And I updated the packaging for this version already.
Great :D
>> - and I'd like to provide also testing/unstable versions
>Again, let's keep it simple first.
Sure, it was just a wish :)
Bye
Andrea
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
