Skip to contentSkip to conversation

Add libapr-package

PATCH New Rico Bachmann 3 participants 6 messages Apr 17, 2012 – Apr 27, 2012

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Add libapr-package

Add libapr-package
rename from libapr to apr
rename all values and arguments from libapr into apr change package/Config.in from libapr to apr add the other small changes from mailinglist

#1 lore raw

PATCH 1/1 Add apr-package

---
 package/Config.in     |    1 +
 package/apr/Config.in |    8 ++++++++
 package/apr/apr.mk    |   18 ++++++++++++++++++
 3 files changed, 27 insertions(+), 0 deletions(-)
 create mode 100644 package/apr/Config.in
 create mode 100644 package/apr/apr.mk
package/Config.in +1 -0
index 4c6d4d8..bf1bdcf 100644
@@ -372,6 +372,7 @@ source "package/zeromq/Config.in"
 endmenu
 
 menu "Other"
+source "package/apr/Config.in"
 source "package/fftw/Config.in"
 source "package/libargtable2/Config.in"
 source "package/argp-standalone/Config.in"
package/apr/Config.in new file +8 -0
new file mode 100644
index 0000000..292cadb
@@ -0,0 +1,8 @@
+config BR2_PACKAGE_APR
+	bool "apr"
+	help
+	  The mission of the Apache Portable Runtime (APR) project is to create
+	  and maintain software libraries that provide a predictable and
+	  consistent interface to underlying platform-specific implementations
+
+	  http://apr.apache.org/
package/apr/apr.mk new file +18 -0
new file mode 100644
index 0000000..3158913
@@ -0,0 +1,18 @@
+#############################################################
+#
+# apr
+#
+#############################################################
+APR_VERSION = 1.4.6
+APR_SITE = http://archive.apache.org/dist/apr
+APR_INSTALL_STAGING = YES
+APR_CONF_ENV = \
+	ac_cv_file__dev_zero=yes \
+	ac_cv_func_setpgrp_void=yes \
+	apr_cv_process_shared_works=yes \
+	apr_cv_mutex_robust_shared=no \
+	apr_cv_tcp_nodelay_with_cork=yes \
+	ac_cv_sizeof_struct_iovec=8 \
+	apr_cv_mutex_recursive=yes
+
+$(eval $(call AUTOTARGETS))
Signature · 1 line
1.7.2.5
#2 lore raw

PATCH 1/1 Add apr-package

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Rico" == Rico Bachmann <[email protected]> writes:

Rico> Signed-off-by: Rico Bachmann <[email protected]>

Committed, thanks.

Signature · 1 line
Bye, Peter Korsgaard
#3 lore raw

PATCH 1/1 Add libapr-package

In reply to Rico Bachmann
Quoted 6 lines · On Tuesday 17 April 2012 16:35:15 Rico Bachmann wrote:

Add libapr-package
rename from libapr to apr
rename all values and arguments from libapr into apr change package/Config.in from libapr to apr add the other small changes from mailinglist

Hoi Rico,

Thanks for your persistence in correcting your patch until it was perfect!

One last suggestion for next time you make a patch: you can add the log
of the history of your patch directly in the commit message, below a line with three dashes, like this:

---
v3: Rename from libapr to apr
v2: ...

When the patch is applied to git, the part below the --- will be
removed, so you can also add other random comments in there.

And also, you can add the version number when sending the patch
like this:

git send-email --subject-prefix='PATCH v2' ...

Regards,
Arnout

Signature · 6 lines
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
#4 lore raw

PATCH 1/1 Add libapr-package

Quoted 20 lines

-----Urspr?ngliche Nachricht-----
Von: Arnout Vandecappelle [mailto:arnout at mind.be]
Gesendet: Samstag, 21. April 2012 14:58
An: buildroot at busybox.net
Cc: Rico Bachmann
Betreff: Re: [Buildroot] [PATCH] Add libapr-package

Quoted 6 lines · On Tuesday 17 April 2012 16:35:15 Rico Bachmann wrote:

Add libapr-package
rename from libapr to apr
rename all values and arguments from libapr into apr change package/Config.in from libapr to apr add the other small changes from mailinglist

Hoi Rico,

Thanks for your persistence in correcting your patch until it was
perfect!

Quoted 8 lines

One last suggestion for next time you make a patch: you can add the
log of the history of your patch directly in the commit message, below a line with three dashes, like this:

---
v3: Rename from libapr to apr
v2: ...

I'll try that with my new patch for apr-util.
How can I add my history when I have to do a git rebase -I master?

Because I can't see my history in the patch after a fixup with git rebase.

Do I have to add them manually?

Quoted 9 lines

When the patch is applied to git, the part below the --- will be
removed, so you can also add other random comments in there.

And also, you can add the version number when sending the patch like
this:

git send-email --subject-prefix='PATCH v2' ...

I'll try that if I need a v2 from my next patch.

Quoted 6 lines

Regards,
Arnout

Quoted 8 lines

--

Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR
Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

Thanks for the hints!

Regards
Rico

Tofwerk AG, Rico Bachmann
+41 33 511 11 69
bachmann at tofwerk.com
http://www.tofwerk.com
Uttigenstrasse 22
CH - 3600 Thun

#5 lore raw

PATCH 1/1 Add libapr-package

Quoted 9 lines · On Tuesday 24 April 2012 11:32:52 Rico Bachmann wrote:
Quoted 8 lines

One last suggestion for next time you make a patch: you can add the
log of the history of your patch directly in the commit message, below a line with three dashes, like this:

---
v3: Rename from libapr to apr
v2: ...

Quoted 6 lines

I'll try that with my new patch for apr-util.
How can I add my history when I have to do a git rebase -I master?

Because I can't see my history in the patch after a fixup with git rebase.

Do I have to add them manually?

Indeed, git rebase is the same as applying the patch from a mail... You
can either fix up the commit message manually, or use something like topgit to manage your patch queues.

Regards,
Arnout

Signature · 6 lines
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F