On Tue, 2010-03-02 at 16:39 +0100, Martin Bähr wrote:
> On Tue, Mar 02, 2010 at 04:21:45PM +0100, ermo | Rune Morling wrote:
> > What I'm trying to say is that there are still some niggles with Byobu
> > that are entirely my fault -- the packaging needs some work before it is
> > ready for production use.
>
> that's what development and testing is for.
> can you share what the niggles are, so it is easier to get around them
> (or even fix them)? :-)
eMBee,
Byobu is distributed without a Makefile in the traditional sense.
Instead, it's simply a set of files which adhere to the Linux FHS and
which are copied to the filesystem with cp -ar /etc/ ${BUILDROOT} and cp
-ar /usr/ ${BUILDROOT} in the .deb.
I've copied that behaviour in the recipe[1] with r.Run(), but this
apparently means that some files are not included when Conary creates
the package, even though it seems that the files are present in both
%(builddir)s and %(destdir)s. The files missing are configuration files
that are supposed to live under /usr/share and which byobu tries to
source when it starts -- this is why the <F9> key doesn't work, for
instance.
That's the extent of my investigation. Pointers are most welcome.
- ermo
[1]
http://www.rpath.org/web/repos/ermo/getFile?path=byobu.recipe;pathId=28f2c1913ee5287b0f4099ef0d50efc2;fileId=35b37eedb3139688a69e1977a2a048d98ce3fc2d;fileV=/ermo.rpath.org%40fl%3A2-devel/2.59-3
_______________________________________________
Foresight-devel mailing list
Foresight-devel@lists.rpath.org
http://lists.rpath.org/mailman/listinfo/foresight-devel
