On Monday 26 October 2009 00:17:06 Jeremiah Foster wrote:
> Now we just need to get MUD to do recursive package building and
> package all the missing dependencies!
Although that was a joke, it sort of tries to do that! If there is dependency
will have a go at building that. It doesn't work, in
On Oct 25, 2009, at 21:59, Graham Cobb wrote:
> On Friday 23 October 2009 14:10:52 Marius Gedminas wrote:
>> On Fri, Oct 23, 2009 at 02:13:57PM +0200, Jeremiah Foster wrote:
>>> The best way to go about it might be to first pull down your source
>>> package from upstream. Upstream is usually debi
I appreciate all the responses. As i suspected, this is one of those
things that is confusing when starting out, but very straightforward
once up to speed.
I have the package for libmikmod2 ready to upload when i get
permission, and have also got the much more challenging game package
that depends
On Friday 23 October 2009 14:10:52 Marius Gedminas wrote:
> On Fri, Oct 23, 2009 at 02:13:57PM +0200, Jeremiah Foster wrote:
> > The best way to go about it might be to first pull down your source
> > package from upstream. Upstream is usually debian and that is easy to
> > do if you are on a debia
On Fri, Oct 23, 2009 at 02:13:57PM +0200, Jeremiah Foster wrote:
> The best way to go about it might be to first pull down your source
> package from upstream. Upstream is usually debian and that is easy to
> do if you are on a debian, or even debian-like, machine:
>
> `apt-get source li
On Oct 23, 2009, at 11:39, David Falkayn wrote:
> I'm talking about a typical workflow; what steps would probably be
> necessary to take a library that's available as a .deb somewhere and
> make it available on Maemo? If i knew the specifics, i guess i wouldn'
> t need to ask, but there are some
I'm talking about a typical workflow; what steps would probably be
necessary to take a library that's available as a .deb somewhere and
make it available on Maemo? If i knew the specifics, i guess i wouldn'
t need to ask, but there are some general steps like (1) get source
package (2) modify packa
El vie, 23-10-2009 a las 00:37 -0400, David Falkayn escribió:
> Here's a question for you whiz kids: what's the best way to go about
> packaging up a library that already exists, e.g. in debian, for Maemo?
>
> Presumably the process is easier than starting from scratch, but after
> fiddling around
Here's a question for you whiz kids: what's the best way to go about
packaging up a library that already exists, e.g. in debian, for Maemo?
Presumably the process is easier than starting from scratch, but after
fiddling around with various things and some nice help on IRC, i got
nuttin.
__
Hi,
Johan Bilien wrote:
> One of the dependency is gtkmm, which could be useful to others, so it
> would be good to have it as a separate package. Could it be included in
> the maemo platform?
in this context it would be useful to have a list of libraries which will be
included the final platform
Hi all,
I'm trying to package minisip, which depends on a few libraries that are
not in the maemo platform. How should I package everything? The "Making
a package for the Application Installer" howto recommends building
self-contained packages, with no dependencies. So should I link the
applicatio
11 matches
Mail list logo