=== Amaranthus is now known as Amaranth
=== yofel_ is now known as yofel
=== xdatap is now known as xdatap1
=== Quintasan_ is now known as Quintasan
=== ninjak_ is now known as ninjak
[12:13] <aboudreault> Hi. Is there any tutorial to convert a package to have a multi-version package? a bit like postgresql-8.4, postgresql-9.1
[12:27] <tumbleweed> aboudreault: I think it's mostly common sense: Figure out how to move anything that may clash
[12:27] <aboudreault> there's no standard and/or policies ?
[12:28] <tumbleweed> well, we try and avoid having multiple versions of the same package in the archive at the same time
[12:28] <tumbleweed> so thepolicy is: don't do it if you can possibly avoid it
[12:29] <aboudreault> Ok... I have a lot of clients that see the need to have/test all versions of our software.. :(
[12:43] <geser> aboudreault: are you trying to build your package for multiple versions of a dependency or to have multiple versions co-installable?
[12:44] <aboudreault> yes, sorry. I want something co-installable.
[12:45] <aboudreault> well.... I will keep my current version as it is....... But I want to provide in example: cgi-mapserver-5.6, cgi-mapserver-6.0
[12:55] <geser> then you need to have seperate (versioned) source and binary package names and need to take care that no files clashes
[13:01] <geser> it would be enough if your 1 source package builds "versioned" binary packages if you don't need to work on them later, i.e "cgi-mapserver" (source package) builds now "cgi-mapserver-5.6", after an update it builds "cgi-mapserver-6.0"
[13:06] <aboudreault> geser, hmm... not sure to follow you my source package cannot build the two versions
[13:08] <aboudreault> haa ok, I see what you means
[13:08] <aboudreault> you mean using some variable and some debian/file.in to get things done automatically.
[13:08] <aboudreault> yeah, would be the best
[13:13] <geser> aboudreault: your source package can only hold one version therefore you need a version in the source package name if you want to be able to work on older versions later again (e.g. provide a newer revision)
[13:14] <aboudreault> yes
[13:14] <geser> -> multiple source packages (foo-1.0, foo-1.1, foo-2.0, ...)
[13:15] <geser> and each source package builds binary packages which include the version in there name (foo-bin-1.0, foo-bin-1.1, foo-bin-2.0)
[13:17] <geser> as I don't know how often your version changes that a generated file is needed or if doing some sed after copying the source package for the new version is enough
=== nigelbabu is now known as nigelb
=== JanC_ is now known as JanC
=== jalcine is now known as Jacky