On Sat, Feb 8, 2014 at 1:03 AM, Roelof Wobben wrote:
> But it seems that some makefiles are not well written, Cinnamon
> will not compile and clean well.
If you have a specific question, please ask it.
> Is there someone who can work with me so I can learn to make
> this work for De
Hello,
I try to pot Cinnamon to Debian.
But it seems that some makefiles are not well written, Cinnamon
will not compile and clean well.
Is there someone who can work with me so I can learn to make
this work for Debian.I knowI have to read a lot about this
That's not a problem.
R
Your message dated Sun, 28 Apr 2013 16:22:55 +
with message-id
and subject line closing RFS: gmsl/1.1.3-2 [ITP] - Useful functions for
Makefiles
has caused the Debian Bug report #694774,
regarding RFS: gmsl/1.1.3-2 [ITP] - Useful functions for Makefiles
to be marked as done.
This means that
Section : devel
It builds those binary packages:
gmsl - extra functions to extend functionality of GNU Makefiles
To access further information about this package, please visit the following
URL:
http://mentors.debian.net/package/gmsl
Alternatively, one can download t
ction : devel
>
> It builds these binary packages:
> bakefile - Cross-compiler native makefiles generator
Some comments:
* The original source has some copyright notes that are not mention on you
debian/copyright
* You are shipping an embeded copy of python-empy, it would be bett
ese binary packages:
bakefile - Cross-compiler native makefiles generator
The package appears to be lintian clean.
The upload would fix these bugs: 496832
My motivation for maintaining this package is:
I need this package because is a dependency of other ITP and also is
a software that facil
Dmitrijs Ledkovs wrote:
> I have a lot of manpages written in pod and instead of 15 lines in
> rules I want to have just 3.
> It's not quite working though =(((
>
> ./debian/rules -n build/manpages
> for i in addld mkfastmod mod2imp osis2mod imp2gbs imp2ld imp2vs
> vpl2mod vs2osisref tei2mod xml2
[Eugene V. Lyubimkin, 2009-05-18]
> Dmitrijs Ledkovs wrote:
> > ./debian/rules -n build/manpages
> > for i in addld mkfastmod mod2imp osis2mod imp2gbs imp2ld imp2vs
> ^
>
Dmitrijs Ledkovs wrote:
> I have a lot of manpages written in pod and instead of 15 lines in
> rules I want to have just 3.
> It's not quite working though =(((
>
> ./debian/rules -n build/manpages
> for i in addld mkfastmod mod2imp osis2mod imp2gbs imp2ld imp2vs
I have a lot of manpages written in pod and instead of 15 lines in
rules I want to have just 3.
It's not quite working though =(((
./debian/rules -n build/manpages
for i in addld mkfastmod mod2imp osis2mod imp2gbs imp2ld imp2vs
vpl2mod vs2osisref tei2mod xml2gbs installmgr; do
pod2man --release= -
On Mon, Apr 10, 2006 at 05:18:46PM +0100, Darren Salt wrote:
> I demand that Carlo Segre may or may not have written...
>
> > On Sun, 9 Apr 2006, David Liontooth wrote:
> [snip]
> >> I need a bit more help -- where do I add them to rules?
>
> >> CFLAGS = -Wall -g
>
> >> Can I add the "Link wit
I demand that Carlo Segre may or may not have written...
> On Sun, 9 Apr 2006, David Liontooth wrote:
[snip]
>> I need a bit more help -- where do I add them to rules?
>> CFLAGS = -Wall -g
>> Can I add the "Link with" line to give
>> CFLAGS = -Wall -g -lGLU -lGL -lXmu -lXext -lX11
[snip]
>
On Sun, 9 Apr 2006, Justin Pryzby wrote:
On Sun, Apr 09, 2006 at 09:45:02AM -0500, Carlo Segre wrote:
On Sun, 9 Apr 2006, David Liontooth wrote:
Roberto C. Sanchez wrote:
I would just put those into the debian/rules. There is not enough there
to justify a full-blown makefile in my mind.
On Sun, Apr 09, 2006 at 09:45:02AM -0500, Carlo Segre wrote:
> On Sun, 9 Apr 2006, David Liontooth wrote:
>
> >Roberto C. Sanchez wrote:
> >>
> >>I would just put those into the debian/rules. There is not enough there
> >>to justify a full-blown makefile in my mind.
> >>
> >OK, that's good news,
On Sun, 9 Apr 2006, David Liontooth wrote:
Roberto C. Sanchez wrote:
I would just put those into the debian/rules. There is not enough there
to justify a full-blown makefile in my mind.
OK, that's good news, but I need a bit more help -- where do I add them to
rules?
CFLAGS = -Wall -g
On Sun, Apr 09, 2006 at 01:20:06AM -0700, David Liontooth wrote:
> Roberto C. Sanchez wrote:
> >David Liontooth wrote:
> >
> >>I occasionally run into tarballs without a makefile. How do I turn those
> >>into Debian packages?
> >>
> >>Here's an example -- otk_lib from http://otk.sourceforge.net/.
Roberto C. Sanchez wrote:
David Liontooth wrote:
I occasionally run into tarballs without a makefile. How do I turn those
into Debian packages?
Here's an example -- otk_lib from http://otk.sourceforge.net/.
# tar zxvf otk_lib_0.47.tgz
otk_lib/gadget_lib.c
otk_lib/letter2vector2.c
otk_lib/ot
David Liontooth wrote:
> I occasionally run into tarballs without a makefile. How do I turn those
> into Debian packages?
>
> Here's an example -- otk_lib from http://otk.sourceforge.net/.
>
> # tar zxvf otk_lib_0.47.tgz
> otk_lib/gadget_lib.c
> otk_lib/letter2vector2.c
> otk_lib/otk_lib.c
> otk_
I occasionally run into tarballs without a makefile. How do I turn those
into Debian packages?
Here's an example -- otk_lib from http://otk.sourceforge.net/.
# tar zxvf otk_lib_0.47.tgz
otk_lib/gadget_lib.c
otk_lib/letter2vector2.c
otk_lib/otk_lib.c
otk_lib/Readme.txt
otk_lib/gadget_lib.h
otk_l
Andreas Fester wrote:
Hi,
kamaraju kusumanchi wrote:
[...]
>> http://sources.redhat.com/autobook/
[...]
> The above autobook contains information about very old tools. Though
the
> concepts might remain same, I have difficulty reading it. Every time I
> try something and if it does not work,
Hi,
kamaraju kusumanchi wrote:
[...]
>> http://sources.redhat.com/autobook/
[...]
> The above autobook contains information about very old tools. Though the
> concepts might remain same, I have difficulty reading it. Every time I
> try something and if it does not work, I keep wondering whether i
Andreas Fester wrote:
Another good manual regarding autoconf and automake
(that is, makefiles.am and makefiles.in) is
http://sources.redhat.com/autobook/
It is also in english though
Best Regards,
Andreas
The above autobook contains information about very old tools. Though the
co
On Thu, Jul 07, 2005 at 11:39:37AM +0200, PY LUYTEN wrote:
> Hello
>
> i try to learn a bit as it seems i am not ready to develop any package.
> I tryed the maintener guide but need more docs about makefiles,
> makefiles.am and makefiles.in and could not find it - "man"
ready to develop any package.
I tryed the maintener guide but need more docs about makefiles,
makefiles.am and makefiles.in and could not find it - "man" being not
enough for me.
Did i miss a good doc (especially in french) ?
[...]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
On 7/7/05, PY LUYTEN <[EMAIL PROTECTED]> wrote:
> i try to learn a bit as it seems i am not ready to develop any package.
> I tryed the maintener guide but need more docs about makefiles,
> makefiles.am and makefiles.in and could not find it - "man" being not
> enough
Hello
i try to learn a bit as it seems i am not ready to develop any package.
I tryed the maintener guide but need more docs about makefiles,
makefiles.am and makefiles.in and could not find it - "man" being not
enough for me.
Did i miss a good doc (especially in french) ?
Tha
Quoting Colin Watson <[EMAIL PROTECTED]> (2003-09-09 00:50:24 BST):
> On Mon, Sep 08, 2003 at 07:22:02PM -0400, Neil Roeth wrote:
> > I recently read about target-specific variables in make, so I thought I
> > could
> > do this:
> >
> > pkg1-stamp: pkg1
> > pkg2-stamp: pkg2
> >
> > %-stamp: $(@:
Quoting Colin Watson <[EMAIL PROTECTED]> (2003-09-09 00:50:24 BST):
> On Mon, Sep 08, 2003 at 07:22:02PM -0400, Neil Roeth wrote:
> > I recently read about target-specific variables in make, so I thought I could
> > do this:
> >
> > pkg1-stamp: pkg1
> > pkg2-stamp: pkg2
> >
> > %-stamp: $(@:%-sta
On Sep 9, Colin Watson ([EMAIL PROTECTED]) wrote:
> On Mon, Sep 08, 2003 at 07:22:02PM -0400, Neil Roeth wrote:
> > I recently read about target-specific variables in make, so I thought I
> > could
> > do this:
> >
> > pkg1-stamp: pkg1
> > pkg2-stamp: pkg2
> >
> > %-stamp: $(@:%-stamp=
On Sep 9, Colin Watson ([EMAIL PROTECTED]) wrote:
> On Mon, Sep 08, 2003 at 07:22:02PM -0400, Neil Roeth wrote:
> > I recently read about target-specific variables in make, so I thought I could
> > do this:
> >
> > pkg1-stamp: pkg1
> > pkg2-stamp: pkg2
> >
> > %-stamp: $(@:%-stamp=%)
>
On Mon, Sep 08, 2003 at 07:22:02PM -0400, Neil Roeth wrote:
> I recently read about target-specific variables in make, so I thought I could
> do this:
>
> pkg1-stamp: pkg1
> pkg2-stamp: pkg2
>
> %-stamp: $(@:%-stamp=%)
> touch $@
>
> pkg1: DH_OPTIONS=-p$@
> ...
> dh_install
>
I have a source package that creates multiple binary packages, each of which
requires a different sequence of debhelper programs. To avoid having to
specify the -p option for each command, I do this:
pkg1-stamp: pkg1
pkg2-stamp: pkg2
%-stamp:
$(MAKE) -f debian/rules DH_OPTIONS=-p$(@:%-st
On Mon, Sep 08, 2003 at 07:22:02PM -0400, Neil Roeth wrote:
> I recently read about target-specific variables in make, so I thought I could
> do this:
>
> pkg1-stamp: pkg1
> pkg2-stamp: pkg2
>
> %-stamp: $(@:%-stamp=%)
> touch $@
>
> pkg1: DH_OPTIONS=-p$@
> ...
> dh_install
>
I have a source package that creates multiple binary packages, each of which
requires a different sequence of debhelper programs. To avoid having to
specify the -p option for each command, I do this:
pkg1-stamp: pkg1
pkg2-stamp: pkg2
%-stamp:
$(MAKE) -f debian/rules DH_OPTIONS=-p$(@:%-st
34 matches
Mail list logo
