Re: [Fink-devel] Package and Version strings (was Re: [Fink-i18n] [translate] Fwd: web/xml/packaging packaging.en.xml,1.23,1.24)
Okay, any objections to saying that Version and Revision "must" begin with numbers? Or should we weaken the statement slightly to say "should" begin with numbers? FWIW, there are currently about 5 packages that do not conform to this. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Still >500 packages not moved from 10.2 tree, need help
On Apr 19, 2004, at 6:45 PM, David R. Morrison wrote: We need a mechanism to mark packages as "should not be moved to 10.3", especially if there is going to be a general call to action like this. This is done. See http://fink.sourceforge.net/pdb/compare.php now. Maintainers can change the status of their packages to green (dont move) red (can't move, won't compile) or white (move me). -Ben --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Still >500 packages not moved from 10.2 tree, need help
I maintain three of those (skycal, socat and sswf) but am still on 10.2.8. I'll be happy to resume maintainership when I upgrade, but in the meantime porting assistance would be appreciated. socat and skycal are pretty simple. Chris On Monday, April 19, 2004, at 06:46 PM, Ben Hines wrote: Still > 500 pkgs show 'not moved' from 10.2-gcc3.3 to 10.3. A number of these are obsolete, but many are not. Anyone with commit access feel free to move over anything that works. (I usually start them out in the 10.3 tree with the new filename format, but be sure to fix any references to the patch file in the info) If a maintainer no longer desires to maintain a package they can remove their names from the maintainer line once it is in the 10.3 tree, but the package should still be moved. (with a 'None' maintainer) list: http://homepage.mac.com/bhines/finknotmoved.html -Ben -- Chris Dolan, Software Developer, Clotho Advanced Media Inc. 608-294-7900, 211 S Paterson Suite 260, Madison WI 53703 PGP.sig Description: This is a digitally signed message part
Re: [Fink-devel] Source field in var/lib/dpkg/available
On Tue, Apr 20, 2004 at 04:25:37PM +0300, Antti Tapaninen wrote:
> On Mon, 19 Apr 2004, Daniel Macks wrote:
> >
> > fink dumpinfo --source > output.txt
> >
> > (or something like that...the exact syntax isn't quite set yet) and
> > then you can browse a giant listing of all packages (or optionally
> > limitted by package name) and their macro-expanded tarball names at
> > your leisure. Would that provide the kind of info you want?
>
> Probably, but then I would have to make two separate tools, one for
> standard debian and other for Fink. :)
Wait, I think I answered the wrong question ("source" meaning the
tarball of .c files, not the parent package name).
> I still don't understand why Fink needs to keep both Source and Package
> fields in the final .deb file information identical, I managed to modify
> fink packaging routines so that it'll generate the packages into same form
> as Debian does. This way I can easily determine for my owns statistics the
> original source and version, of which the package(s) have been generated.
>
> Here's the change that I made:
>
> --- /sw/lib/perl5/Fink/PkgVersion.pm.orig Tue Apr 20 15:52:37 2004
> +++ /sw/lib/perl5/Fink/PkgVersion.pm Tue Apr 20 16:09:47 2004
> @@ -1722,7 +1722,7 @@
> $instsize = $self->get_instsize("$destdir$basepath");
> $control = < Package: $pkgname
> -Source: $pkgname
> +Source: $self->{_expand}->{N}
> Version: $version
> Section: $section
> Installed-Size: $instsize
That indeed does look s like a bug. Appears to be unchanged when
SplitOffs (child packages) got implemented.
At least for fink, is the kind of thing you want?
% fink showparent gle3-shlibs
gle3-shlibs's parent is gle3.
% fink showparent gle3
gle3 is the parent.
% fink splitoffs gle3
gle3 has 1 child:
-> gle3-shlibs
% fink splitoffs gle3-shlibs
gle3-shlibs is a child, it's parent gle3 has 1 child:
-> gle3-shlibs
It's in fink now, but is completely undocumented.
> The tool that I started working on yesterday is at
> http://www.hut.fi/~aet/dpkg-glue. If anyone knows the correct spell that
> does about the same with standard dpkg/apt tools, please let me know. :)
The dpkg-* tools are the usual way to construct and manipulate .deb
archives and the various databasefiles. Have you looked at dpkg-query,
dpkg-scanpackages, and dpkg-deb? OTOH, it may be more efficient to
just read the files themselves as you are doing now.
dan
--
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Source field in var/lib/dpkg/available
On Mon, 19 Apr 2004, Daniel Macks wrote:
Hi,
> There's a feature in the not-yet-released version of fink that lets
> you extract this type of info directly from fink's own database. You
> will be able to
>
> fink dumpinfo --source > output.txt
>
> (or something like that...the exact syntax isn't quite set yet) and
> then you can browse a giant listing of all packages (or optionally
> limitted by package name) and their macro-expanded tarball names at
> your leisure. Would that provide the kind of info you want?
Probably, but then I would have to make two separate tools, one for
standard debian and other for Fink. :)
I still don't understand why Fink needs to keep both Source and Package
fields in the final .deb file information identical, I managed to modify
fink packaging routines so that it'll generate the packages into same form
as Debian does. This way I can easily determine for my owns statistics the
original source and version, of which the package(s) have been generated.
Here's the change that I made:
--- /sw/lib/perl5/Fink/PkgVersion.pm.orig Tue Apr 20 15:52:37 2004
+++ /sw/lib/perl5/Fink/PkgVersion.pmTue Apr 20 16:09:47 2004
@@ -1722,7 +1722,7 @@
$instsize = $self->get_instsize("$destdir$basepath");
$control = <{_expand}->{N}
Version: $version
Section: $section
Installed-Size: $instsize
The tool that I started working on yesterday is at
http://www.hut.fi/~aet/dpkg-glue. If anyone knows the correct spell that
does about the same with standard dpkg/apt tools, please let me know. :)
Cheers,
-Antti
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [tutors-dev:00402] Re: [Fink-devel] Re: dists/10.3/unstable/main/finkinfo/text cwtext.info,NONE,1.1
Our team are going to discuss it at the next meeting. Thanks for advice! AIDA Shinra Univ. of Tokyo Educational Computing System Tutors --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
