Bug#458812: Could not build package.
Hello,
On Thu, Aug 6, 2009 at 2:42 PM, Adam C Powell IV<hazelsct@debian.org> wrote:
> Hello,
>
> ...
> Great, thanks for the report!
No problem. It just good to know, that after a couple of days I could
spot the problems.
>> Further on, continuing topic of Aster/Salome packaging, if I may.
>> Currently, newer
>> versions of Code Aster (10.0.3) and Salome platform (5.1.2, Qt4
>> remake) are available. Having
>> look at debianization as it is done now, I understand that it is a
>> hell of a job to package this
>> pieces of software, especially when there is no (as I understood from
>> discussion here and
>> elsewhere) any link with upstream...
>
> Indeed, that's why I haven't updated those packages in so long. :-(
>
>> But hence there is some expertise
>> around, may people
>> currently involved in packaging make some overview on what would be good to do
>> with respect to Aster/Salome build/deployment tools to simplify actual
>> packaging, and hence
>> faster deployment of newer versions of the software in the future? May
>> be there is something
>> like that already available?
>
> Yes, I think this bug is a good forum for people to use. I'd be happy
> to put some more time into getting it working, but a team packaging
> approach, or someone else packaging it, is fine with me too.
I tried to summarize my findings of last few days on the current state
of Code_Aster building/deployment practices and its relation to
packaging efforts in the RFC posted on Code_Aster forum [1]. I hope
that this topic will start some discussion, although I have to admit
that I am a bit skeptical now.
I am going to invest a bit more time to compare state of the
building/deployment in the latest version of Code_Aster to packaged
9.2. But first... I have to do more in learning how to package (lots
of RTFM).
[1] http://www.code-aster.org/forum2/viewtopic.php?id=13292
Reply to: