Closed GoogleCodeExporter closed 8 years ago
He !
I have a small linux system build from scratch, and i would to install opkg and
build some packages to maintain it easily.
But, there is no automated system for creating packages, it's really important
to add it !
cheers,
sstorme
Original comment by atel...@atelier-web.com
on 25 Jul 2010 at 6:40
Until someone steps up to maintain it, this will not happen. Both openwrt and
openembedded have patches against ipkg-utils that you may be interested in
looking at.
Original comment by graham.g...@gmail.com
on 2 Aug 2010 at 11:56
I've started looking at this since i need it as well. But I've been trying to
decide if it should be separate utilities or built into opkg, so you'd have
something like "opkg-cl buildpackage" or "opkg-buildpackage".
Original comment by gary.kra...@gmail.com
on 21 Feb 2011 at 10:34
The {i,o}pkg-utils scripts are in heavy use by several major projects. They are
not going away any time soon. Mostly, it would just be a good idea for these
projects to pool their resources by applying patches to a common tree.
Putting this functionality into opkg-cl, as C code, would only serve to make
opkg code more of a tangle than it already is.
Original comment by graham.g...@gmail.com
on 21 Feb 2011 at 11:01
well at the very least I'd think it should be using libopkg to make sure
formats are correct...
Original comment by gary.kra...@gmail.com
on 22 Feb 2011 at 3:07
It can't use libopkg. There is no code for writing tar/ar/gzip files.
I agree that from a design point of view, most of the functionality required
from opkg-cl/opkg-utils should be deduplicated and common code should go into
the library. Unfortunately the design of opkg does not lend itself to doing
this.
FYI, I have grandiose plans for a rewrite which would do what you are
proposing. Its not likely to be ready for some time however.
Original comment by graham.g...@gmail.com
on 22 Feb 2011 at 3:12
Well I'm willing to help where I can. So if you have a starting point, I can
jump in. I was also looking for an api reference but couldn't find one. So
maybe some doxygen love (or any other documentation tool) could be applied as
well.
Original comment by gary.kra...@gmail.com
on 23 Feb 2011 at 12:12
[deleted comment]
If anyone ever gets to this, another patch that needs to be included (broken in
the openmoko repository and release pkg) that causes OE builds to fail on
systems using likewise-open and possibly other situations where the UUID and
GUID fill the header fields (so parsing with split() doesn't end up with the
right number of elements):
--- ipkg-utils.old/arfile.py 2009-03-13 12:45:25.937148714 -0400
+++ ipkg-utils/arfile.py 2009-03-13 12:44:59.680250619 -0400
@@ -74,7 +74,14 @@
if l == "\n":
l = self.f.readline()
if not l: break
- descriptor = l.split()
+ descriptor = [ l[0:15].strip() # filename
+ , l[16:27].strip() # timestamp
+ , l[28:33].strip() # owner ID
+ , l[34:39].strip() # gid
+ , l[40:47].strip() # mode
+ , l[48:57].strip() # size in bytes
+ , l[58:59].strip() # file magic
+ ]
# print descriptor
size = int(descriptor[5])
Original comment by JamminJ...@gmail.com
on 8 Jun 2011 at 6:28
Please check havily updated version in
http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/
Original comment by Martin.J...@gmail.com
on 30 Jul 2012 at 3:09
For now at least, opkg-utils is separate from opkg. Martin has posted the right
link.
Original comment by paul.betafive
on 3 Aug 2013 at 10:08
Original issue reported on code.google.com by
xvi...@gmail.com
on 8 Mar 2010 at 1:01