[Pkg-ace-devel] Plan for ACE+TAO upload

[Johnny Willemsen]

Hi,


>>> I would suggest that we perform the following renamings:
>>>   - tao-concurrency =>  tao-cosconcurrency
>>>   - tao-event =>  tao-cosevent
>>>   - tao-log =>  tao-tls
>>>   - tao-naming =>  tao-cosnaming
>>>   - tao-notify =>  tao-cosnotification
>>>   - tao-trading =>  tao-costrading
>>> to follow Ken's RPM naming. I believe we should provide
>>> transitional packages for these renamings.
>>
>> See ACE_wrappers/rpmbuild for the current rpm file
>
> You mean rpmbuild from DOC SVN repo completely replaces Ken's
> RPM?
Ken is still shipping his version of the packaged file, but from the
doc_group side we use ACE_wrappers/rpmbuild and publish rpm's through
opensuse build service for suse, rhel, and some more platforms.
>>> Should we distribute these? Is anything missing?
>> We can distribute them, but let us do that later, first get x.7.8
>> packaged. x.7.9 is schedule for the week of May 17th, x.8.0 for July
>> 1st.
>
>
> My question was not whether these services are compiled or distributed
> in RPM. Nor what is the faster way to get up-to-date ACE+TAO Debian
> packages. Again Johnny, we're seeking different goals: the version that
> will be packaged in the next Debian version will have to be supported
> by Debian maintainers. I will not choose the quick win method for
> Debian. And we do not share the same planning; as a Debian developper I
> want ACE+TAO packages to be available in Debian with a good quality, a
> fine integration in the OS. Even if this means Debian does not get
> distributed with the latest release of ACE+TAO.
>
> My question was rather: does upstream think these services are worth
> distributing? Are they useful or just a incomplete implementation? For
> the record they are distributed as of today.

Let us distribute them on debian. To be clear, I was also aiming at a
good and stable package, I only wanted to see if there is a way to make
some steps forward. When the packaging files are there and any generic
issues are resolved in ACE/TAO, than packaging should be nothing more
than running a script. When there are issues after packaging, report
them back to the ACE/TAO community, we will see how we can assist in
fixing them. When the packaging files are up to date, the release script
can easily update them and than for example through opensuse build
service we can easily build the packages for all OS versions.

Johnny

-------------- next part --------------
A non-text attachment was scrubbed...
Name: jwillemsen.vcf
Type: text/x-vcard
Size: 309 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ace-devel/attachments/20100503/48a3926d/attachment.vcf>