cppqed-support

[Cppqed-support] Ubuntu packages

[Raimar S. <rai...@ui...>]

Dear András,

I have prepared Ubuntu packages for C++QED.

https://launchpad.net/~raimar-sandner/+archive/cppqed

The packages can be installed with

sudo add-apt-repository ppa:raimar-sandner/cppqed
sudo apt-get update
sudo apt-get install c++qed-scripts libc++qed-dev

In addition to blitz-0.10 there are three packages in the repository, each 
compiled for 32 and 64 bit architecture and for the Ubuntu series Quantal, 
Precise and Oneiric (other series can be added):

* libc++qed: the libraries libC++QED.so, libel.so and libutils.so

* libc++qed-dev: the header files and an example cmake project 
/usr/share/doc/libc++qed-dev/examples with all the script source files and an 
CMakeLists.txt which demonstrates how to compile scripts. A Readme.txt in the 
directory explains this.

* c++qed-scripts: the scripts as executables, ready to run.


Distributing new snapshot packages is as easy as pushing to a special bazaar 
repository on launchpad and requesting a build on the web interface.

Can we skype later today?

Best regards
Raimar

Re: [Cppqed-support] Ubuntu packages

[Andras V. <and...@ui...>]

Dear Raimar,

This looks great. Did you create it simply from the main branch? Do
you think it would be possible to add FLENS as a dependency (perhaps
conditionally somehow)?

It would be nice if you could document this a little bit, perhaps we
should publish the packages already on the index page.

Let's skype early afternoon.

Bests,
András




On Mon, Aug 27, 2012 at 10:20 AM, Raimar Sandner
<rai...@ui...> wrote:
> Dear András,
>
> I have prepared Ubuntu packages for C++QED.
>
> https://launchpad.net/~raimar-sandner/+archive/cppqed
>
> The packages can be installed with
>
> sudo add-apt-repository ppa:raimar-sandner/cppqed
> sudo apt-get update
> sudo apt-get install c++qed-scripts libc++qed-dev
>
> In addition to blitz-0.10 there are three packages in the repository, each
> compiled for 32 and 64 bit architecture and for the Ubuntu series Quantal,
> Precise and Oneiric (other series can be added):
>
> * libc++qed: the libraries libC++QED.so, libel.so and libutils.so
>
> * libc++qed-dev: the header files and an example cmake project
> /usr/share/doc/libc++qed-dev/examples with all the script source files and an
> CMakeLists.txt which demonstrates how to compile scripts. A Readme.txt in the
> directory explains this.
>
> * c++qed-scripts: the scripts as executables, ready to run.
>
>
> Distributing new snapshot packages is as easy as pushing to a special bazaar
> repository on launchpad and requesting a build on the web interface.
>
> Can we skype later today?
>
> Best regards
> Raimar
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Cppqed-support mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppqed-support

Re: [Cppqed-support] Ubuntu packages

[Raimar S. <rai...@ui...>]

Dear András,

it is possible to add FLENS, but I would have to create a FLENS package 
because at the moment there is none in Ubuntu. A conditional FLENS dependency 
is only possible if we have two separate packages, one with and one without 
FLENS (e.g. libc++qed and libc++qed_flens). But the FLENS dependency doesn't 
hurt much even for people who don't use it.

At the moment the packages are created directly from my branch cppqed/raimar 
because of some recent changes to cmake, but later we can switch this to 
master. The way it works: on launchpad there is an exact copy of the 
development branch and an additional branch which contains the information how 
to build the packages (checkout lp:~raimar-sandner/+junk/cppqed-debian-build 
if you want to have a look). These two branches are then automatically merged 
and source packages for the various distributions and architectures are 
created and then built on the launchpad build farm.

I would suggest to rename "Installation" to "Installation from source" and add 
a section "Installation from packages". I plan to write a Gentoo ebuild and 
Sebastian could contribute Arch-Linux packages. 

By publishing on the index page, do you mean to provide the .deb files as 
downloads or to give instructions how to install from the repository?

Best regards
Raimar

On Monday 27 August 2012 10:50:59 Andras Vukics wrote:
> Dear Raimar,
> 
> This looks great. Did you create it simply from the main branch? Do
> you think it would be possible to add FLENS as a dependency (perhaps
> conditionally somehow)?
> 
> It would be nice if you could document this a little bit, perhaps we
> should publish the packages already on the index page.
> 
> Let's skype early afternoon.
> 
> Bests,
> András
> 
> 
> 
> 
> On Mon, Aug 27, 2012 at 10:20 AM, Raimar Sandner
> 
> <rai...@ui...> wrote:
> > Dear András,
> > 
> > I have prepared Ubuntu packages for C++QED.
> > 
> > https://launchpad.net/~raimar-sandner/+archive/cppqed
> > 
> > The packages can be installed with
> > 
> > sudo add-apt-repository ppa:raimar-sandner/cppqed
> > sudo apt-get update
> > sudo apt-get install c++qed-scripts libc++qed-dev
> > 
> > In addition to blitz-0.10 there are three packages in the repository, each
> > compiled for 32 and 64 bit architecture and for the Ubuntu series Quantal,
> > Precise and Oneiric (other series can be added):
> > 
> > * libc++qed: the libraries libC++QED.so, libel.so and libutils.so
> > 
> > * libc++qed-dev: the header files and an example cmake project
> > /usr/share/doc/libc++qed-dev/examples with all the script source files and
> > an CMakeLists.txt which demonstrates how to compile scripts. A Readme.txt
> > in the directory explains this.
> > 
> > * c++qed-scripts: the scripts as executables, ready to run.
> > 
> > 
> > Distributing new snapshot packages is as easy as pushing to a special
> > bazaar repository on launchpad and requesting a build on the web
> > interface.
> > 
> > Can we skype later today?
> > 
> > Best regards
> > Raimar
> > 
> > --------------------------------------------------------------------------
> > ---- Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Cppqed-support mailing list
> > Cpp...@li...
> > https://lists.sourceforge.net/lists/listinfo/cppqed-support

Re: [Cppqed-support] Ubuntu packages

[Raimar S. <rai...@ui...>]

Dear András,

I wasn't aware of the different version provided in the universe repository, 
and the naming and versioning is most unfortunate: libboost-serialization-dev 
has version 1.48.0.2 but indeed is a meta-package for version 1.46. 

As far as I know the boost libraries are not binary compatible across 
versions. 

This problem occurs only if the user has explicitly installed the universe 
boost *headers*, if it is only the universe boost libraries everything should 
be fine. And it also happens with standard Ubuntu packages: you should see the 
same conflict when you try to install e.g. libftdipp-dev.

We can do one of the following to work around the problem:

* Unconditionally link against the universe version of boost. Everyone has to 
enable the universe repository to install our package. Apart from that, 
another downside to this approach is that some dev packages in Ubuntu depend 
on the default boost. If one of these is installed there will be a clash 
(similar to the one you experienced only the other way around) when trying to 
install c++qed. Only one version of the boost-dev packages is allowed.

* Provide two separate packages, the default package links against the default 
boost version, and a specialized package links against the universe boost 
version on each series. This way users who don't care which version of boost 
to use (probably most) can just install the default package without worrying 
too much.

* You install your boost version from source and not via apt-get ;)

What do you think?

In both cases we have to use a different build branch for each series, as the 
package names of boost in universe differ across the series. This is not too 
bad, though.

Best regards
Raimar


On Monday 27 August 2012 14:48:40 Andras Vukics wrote:
> Dear Raimar,
> 
> On Precise I have the problem that I had
> libboost-serialization1.48-dev, but libc++qed-dev is looking for
> libboost-serialization-dev, which is I think a meta-package for the
> 1.46 version.
> 
> Can you do something about this?
> 
> Cheers,
> András
> 
> On Mon, Aug 27, 2012 at 1:04 PM, Andras Vukics <and...@ui...> 
wrote:
> > Dear Raimar,
> > 
> >> it is possible to add FLENS, but I would have to create a FLENS package
> >> because at the moment there is none in Ubuntu. A conditional FLENS
> >> dependency is only possible if we have two separate packages, one with
> >> and one without FLENS (e.g. libc++qed and libc++qed_flens). But the
> >> FLENS dependency doesn't hurt much even for people who don't use it.
> > 
> > Right, it should not hurt much, so it could be added as a dependency
> > unconditionally.
> > 
> >> I would suggest to rename "Installation" to "Installation from source"
> >> and add a section "Installation from packages".
> > 
> > Fine.
> > 
> >> By publishing on the index page, do you mean to provide the .deb files as
> >> downloads or to give instructions how to install from the repository?
> > 
> > Perhaps just a link into the Download section of the index page either
> > to the section "Installation from packages" or directly to the
> > launchpad page.
> > 
> > Best regards,
> > András