[puppy-devel] Re: SVN for usr_devx.sfs enhancements?
- From: "Jonathan Marsden" <jmarsden@xxxxxxxxxxx>
- To: puppy-devel@xxxxxxxxxxxxx
- Date: Tue, 07 Feb 2006 22:52:04 -0800
On Tue, 7 Feb 2006, "Fran Boon" <flavour@xxxxxxxxxxxxx> said:
> If we're agreed that updating usr_devx.sfs is a priority then should
> we set up an SVN repository for co-authoring on it? (This could then
> extend to be used for the whole distro)
At this point, I think we'll mostly be packaging existing sources, not
editing them. How do you see SVN or CVS being used in this kind of a
setup? I'm expecting more of a little database of packages with the URL
to a canonical source code tarball, and the parameters needed to build
it under Puppy, and (later) to package it into "user" and "devel" pieces
if necessary. Plus various scripts that use this data to grab tarballs
and package them and run tests against the results. I'm open to other
approaches, though. We could keep the set of scripts under shared
version
control -- is that what you had in mind?
> Any known bugs other than the OpenSSL headers & libexif?
In 1.0.7's usr_devx.sfs, curl is broken because of a missing library:
22:22:40 root@selfhost:~# curl curl: error while loading shared
libraries: libidn.so.11: cannot open shared object file: No such file
or directory 22:22:41 root@selfhost:~#
> If anyone has a list of dependencies for each of the libs, that would
> be great...if not, we should probably start 1...Wiki probably best
> for that?
Can't we automatically produce such a list? Basically run ldd over
every dynamically linked executable in the distribution, recording the
results, and then sorting by library? It doesn't sound like something
that should be created by hand, to me.
Try this (lengthy) one-liner:
for i in `find / -type f -perm +1 |xargs file |grep executable |grep
Intel |grep dynamic |cut -d : -f1 ` ; do echo $i ; ldd $i ; done
as a starting point. It's output is listed by executable, not yet by
lib. It's late, so I'll let someone else post the Perl or awk code to
read this into an assoc array and spit out the info by library -- it's
probably just another one-liner :-)
Hope this helps,
Jonathan
--
Jonathan Marsden
jmarsden@xxxxxxxxxxx
--
http://www.fastmail.fm - Email service worth paying for. Try it for free
- Follow-Ups:
- [puppy-devel] library usage and known missing library bugs
- From: Jonathan Marsden
- [puppy-devel] Re: SVN for usr_devx.sfs enhancements?
- From: Fran Boon
- References:
- [puppy-devel] SVN for usr_devx.sfs enhancements?
- From: Fran Boon
Other related posts:
- » [puppy-devel] SVN for usr_devx.sfs enhancements?
- » [puppy-devel] Re: SVN for usr_devx.sfs enhancements?
- » [puppy-devel] Re: SVN for usr_devx.sfs enhancements?
- » [puppy-devel] Re: SVN for usr_devx.sfs enhancements?
- [puppy-devel] library usage and known missing library bugs
- From: Jonathan Marsden
- [puppy-devel] Re: SVN for usr_devx.sfs enhancements?
- From: Fran Boon
- [puppy-devel] SVN for usr_devx.sfs enhancements?
- From: Fran Boon