From: Carsten Schoenert <c.schoenert@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/opkg: bumping version to 0.2.0
Date: Sat, 5 Oct 2013 20:58:42 +0200 [thread overview]
Message-ID: <1380999522-2915-1-git-send-email-c.schoenert@gmail.com> (raw)
From: Carsten Schoenert <c.schoenert@gmail.com>
opkg has released a new version v0.2.0. The opkg community is also on
the way to switching completely from subversion to git.
The current git repository is placed on Bitbucket and will probably move
once again if there will be find a new home for the project.
https://bitbucket.org/opkg/opkg
The new version 0.2.0 is almost a bugfixing release with a lot of small
changes.
This patch is adding the license info too.
Signed-off-by: Carsten Schoenert <c.schoenert@gmail.com>
---
package/opkg/opkg.mk | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/package/opkg/opkg.mk b/package/opkg/opkg.mk
index 5846433..c57bd7f 100644
--- a/package/opkg/opkg.mk
+++ b/package/opkg/opkg.mk
@@ -4,15 +4,16 @@
#
################################################################################
-OPKG_VERSION = 635
-OPKG_SOURCE = opkg-$(OPKG_VERSION).tar.gz
-OPKG_SITE = http://opkg.googlecode.com/svn/trunk/
-OPKG_SITE_METHOD = svn
+OPKG_VERSION = v0.2.0
+OPKG_SOURCE = $(OPKG_VERSION).tar.bz2
+OPKG_SITE = https://bitbucket.org/opkg/opkg/get
+# Uses PKG_CHECK_MODULES() in configure.ac
+OPKG_DEPENDENCIES = host-pkgconf
+OPKG_LICENSE = GPLv2+
+OPKG_LICENSE_FILES = COPYING
OPKG_INSTALL_STAGING = YES
OPKG_CONF_OPT = --disable-curl
OPKG_AUTORECONF = YES
-# Uses PKG_CHECK_MODULES() in configure.ac
-OPKG_DEPENDENCIES = host-pkgconf
# Ensure directory for lockfile exists
define OPKG_CREATE_LOCKDIR
--
1.8.4.rc3
next reply other threads:[~2013-10-05 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 18:58 Carsten Schoenert [this message]
2013-10-27 11:12 ` [Buildroot] [PATCH] package/opkg: bumping version to 0.2.0 Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1380999522-2915-1-git-send-email-c.schoenert@gmail.com \
--to=c.schoenert@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox