Re: Specifying %{variable} in control file for use in postinst?
156 lines of twisted pre-processing bash code but it works. You can do
a strange merged deb/rpm structure as follows:
~/mypackagedir/distrospecificfilesdir
~/mypackagedir/SPECS
~/mypackagedir/SOURCES
~/mypackagedir/RPMS
etc for rpm.
~/mypackagedir/mypackagedir
~/mypackagedir/mypackagedir/DEBIAN
~/mypackagedir/mypackagedir/mypackageroot
Additionally you can bundle all of the spec file and preprocessing
bash scripts all into DEBIAN since they do not take up much space. I
am going to try to symlink DEBIAN to SPECS and see if it works. I
haven't tried it yet. The above is a way you can mush it all together
into one common subdirectory for both rpm and deb building then move
it around without too much pain from one system to another with the
less duplication.
-- IV
On Sat, May 1, 2010 at 12:07 PM, Ignacio Valdes <ivaldes@hal-pc.org> wrote:
> Moving on.
>
> As suggested I am simply going to have to hack/kludge rpm and deb with
> a bunch of sed pre-processing of the respective spec, control and
> postinst to make it work.
>
> These two divergent schemes put a large burden of effort on developers
> and documenters. Wish I could get deb and rpm folks in the same room
> and say: can you make this easier to do cross-platform work with both
> these package systems like linux filesystem standard?
>
> DEBIAN is roughly equivalent to SPECS: change to a common third like PACK.
> SOURCES is practically the same as the root of DEBIAN, change to a
> common scheme.
> Unify control file and spec header names they are practically the same thing.
>
> -- IV
>
Reply to: