You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(182) |
Nov
(548) |
Dec
(347) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(695) |
Feb
(397) |
Mar
(438) |
Apr
(544) |
May
(367) |
Jun
(273) |
Jul
(160) |
Aug
(247) |
Sep
(204) |
Oct
(308) |
Nov
(467) |
Dec
(406) |
2003 |
Jan
(795) |
Feb
(532) |
Mar
(355) |
Apr
(375) |
May
(352) |
Jun
(312) |
Jul
(290) |
Aug
(157) |
Sep
(130) |
Oct
(261) |
Nov
(532) |
Dec
(480) |
2004 |
Jan
(445) |
Feb
(433) |
Mar
(323) |
Apr
(259) |
May
(126) |
Jun
(175) |
Jul
(219) |
Aug
(286) |
Sep
(178) |
Oct
(144) |
Nov
(141) |
Dec
(133) |
2005 |
Jan
(148) |
Feb
(263) |
Mar
(224) |
Apr
(186) |
May
(283) |
Jun
(243) |
Jul
(138) |
Aug
(124) |
Sep
(109) |
Oct
(90) |
Nov
(295) |
Dec
(164) |
2006 |
Jan
(201) |
Feb
(221) |
Mar
(221) |
Apr
(157) |
May
(87) |
Jun
(131) |
Jul
(97) |
Aug
(93) |
Sep
(174) |
Oct
(112) |
Nov
(208) |
Dec
(166) |
2007 |
Jan
(188) |
Feb
(140) |
Mar
(121) |
Apr
(105) |
May
(95) |
Jun
(131) |
Jul
(131) |
Aug
(72) |
Sep
(152) |
Oct
(116) |
Nov
(222) |
Dec
(237) |
2008 |
Jan
(160) |
Feb
(106) |
Mar
(266) |
Apr
(263) |
May
(150) |
Jun
(140) |
Jul
(224) |
Aug
(119) |
Sep
(105) |
Oct
(103) |
Nov
(71) |
Dec
(52) |
2009 |
Jan
(67) |
Feb
(39) |
Mar
(73) |
Apr
(171) |
May
(113) |
Jun
(90) |
Jul
(160) |
Aug
(129) |
Sep
(270) |
Oct
(117) |
Nov
(88) |
Dec
(97) |
2010 |
Jan
(105) |
Feb
(59) |
Mar
(219) |
Apr
(157) |
May
(128) |
Jun
(168) |
Jul
(87) |
Aug
(100) |
Sep
(95) |
Oct
(50) |
Nov
(61) |
Dec
(31) |
2011 |
Jan
(78) |
Feb
(158) |
Mar
(85) |
Apr
(95) |
May
(50) |
Jun
(37) |
Jul
(66) |
Aug
(24) |
Sep
(50) |
Oct
(79) |
Nov
(79) |
Dec
(51) |
2012 |
Jan
(75) |
Feb
(53) |
Mar
(59) |
Apr
(71) |
May
(78) |
Jun
(90) |
Jul
(83) |
Aug
(74) |
Sep
(82) |
Oct
(35) |
Nov
(10) |
Dec
(22) |
2013 |
Jan
(34) |
Feb
(35) |
Mar
(17) |
Apr
(6) |
May
(27) |
Jun
(53) |
Jul
(27) |
Aug
(19) |
Sep
(23) |
Oct
(58) |
Nov
(68) |
Dec
(24) |
2014 |
Jan
(29) |
Feb
(5) |
Mar
(22) |
Apr
(47) |
May
(73) |
Jun
(75) |
Jul
(13) |
Aug
(76) |
Sep
(40) |
Oct
(78) |
Nov
(53) |
Dec
(28) |
2015 |
Jan
(76) |
Feb
(113) |
Mar
(41) |
Apr
(94) |
May
(48) |
Jun
(41) |
Jul
(15) |
Aug
(8) |
Sep
(62) |
Oct
(67) |
Nov
(28) |
Dec
(5) |
2016 |
Jan
(20) |
Feb
(18) |
Mar
(18) |
Apr
(2) |
May
(10) |
Jun
(46) |
Jul
(11) |
Aug
(34) |
Sep
(10) |
Oct
(33) |
Nov
(30) |
Dec
(1) |
2017 |
Jan
(24) |
Feb
(1) |
Mar
(10) |
Apr
(9) |
May
(8) |
Jun
(5) |
Jul
(9) |
Aug
(17) |
Sep
(13) |
Oct
(23) |
Nov
(16) |
Dec
(14) |
2018 |
Jan
(8) |
Feb
(1) |
Mar
(7) |
Apr
(7) |
May
|
Jun
(3) |
Jul
(10) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
(2) |
Mar
|
Apr
(5) |
May
(1) |
Jun
(3) |
Jul
(5) |
Aug
(16) |
Sep
(3) |
Oct
(8) |
Nov
(3) |
Dec
(3) |
2020 |
Jan
(14) |
Feb
(4) |
Mar
(13) |
Apr
(25) |
May
(11) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(10) |
Dec
(1) |
2021 |
Jan
(5) |
Feb
|
Mar
(2) |
Apr
(11) |
May
(14) |
Jun
(17) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(11) |
2023 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
From: Daniel P. <da...@mw...> - 2001-12-31 00:43:11
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oh, and one more thing... (-; > daniel@gollum /sw$ dpkg -S /sw/info /sw/man > nano: /sw/info > links-ssl, smpeg, r-base, python: /sw/man Tsk, tsk. You should all know better... Daniel - -- PGP public key: http://mwdesign.dyndns.org/~daniel/publickey.txt ACA4 FA04 4033 0569 C626 AA1A C489 25A5 5F67 C125 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (Darwin) Comment: For info see http://www.gnupg.org iD8DBQE8L7SVxIklpV9nwSURAny6AJ9+gN5KElxDGdm1Uv/4h3DsAlJRggCfbwtE 8bxlhdl9aoNcV+gmls9+CWw= =ebgm -----END PGP SIGNATURE----- |
From: Daniel P. <da...@mw...> - 2001-12-31 00:31:42
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just noticed that grace-5.1.5-1, lesstif-0.93.0-2, and tetex- texmf-1.0.2-4 put stuff directly into /sw. It looks like /sw/LessTif is a known issue, but I thought I would report it anyway. Christoph is the maintainer... anyone else want to take it over? Daniel - -- PGP public key: http://mwdesign.dyndns.org/~daniel/publickey.txt ACA4 FA04 4033 0569 C626 AA1A C489 25A5 5F67 C125 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (Darwin) Comment: For info see http://www.gnupg.org iD8DBQE8L7HkxIklpV9nwSURApx0AJ9BuNq7brVNuWvEnsX/0SuEOW0iSQCg8Ja6 iYu55e153Ixp7jqUrOdxBhE= =CGqo -----END PGP SIGNATURE----- |
From: Finlay D. <fin...@bt...> - 2001-12-30 23:28:45
|
On Sunday, December 30, 2001, at 09:23 pm, Bill Bumgarner wrote: > A fixed 2.4.6 (as -2) package has been submitted to the package > tracker. It has been modified to refer to the new location for the > 2.4.6 tarball and should likely be tossed into stable/ immediately > after a second party verifies that it works. No need to bump the revision if it's just a fix like that. I fixed it in CVS, though, just fixed 2.4.6-1 :-) > A 2.5.0-1 package has also been submitted to the package tracker; it > seems to do the correct thing for building 2.5.0 (which involved > disabling IPV6 support) and should be tossed into unstable/ until > enough folks verify that it, in fact, works (works for me). Everything new goes into unstable. Period. -- Finlay |
From: Benjamin R. <ra...@be...> - 2001-12-30 22:08:47
|
I've tried out the new X packages you put together, and I now seem to be missing things like libXext and libX11 when I build gtk+ and such. Did something go missing, or did I do something wrong? |
From: Bill B. <bb...@co...> - 2001-12-30 21:23:51
|
A new version of rsync was released-- 2.5.0-- and this broke the current rsync package in stable/ and unstable/ because the source tarball moved. A fixed 2.4.6 (as -2) package has been submitted to the package tracker. It has been modified to refer to the new location for the 2.4.6 tarball and should likely be tossed into stable/ immediately after a second party verifies that it works. A 2.5.0-1 package has also been submitted to the package tracker; it seems to do the correct thing for building 2.5.0 (which involved disabling IPV6 support) and should be tossed into unstable/ until enough folks verify that it, in fact, works (works for me). b.bum |
From: Jim B. <be...@co...> - 2001-12-30 20:31:50
|
On Saturday, December 29, 2001, at 08:46 PM, Jim Beard wrote: <snip> > manually (omitting the -E) and get the binary to compile. The only > problem being that it seg faults when I run it: > > ... > [localhost:gkrellm-1.2.4-1/gkrellm-1.2.4/src] jim% ./gkrellm > glibtop: netload: eth0 > : Undefined error: 0 > Segmentation fault > ... While looking through so glibtop documentation I found that it returns netload structs for a given interface name. The docs say that the interface name should be the same that appears in ifconfig. So I went ahead and modified the source for gkrellm to ask for en0 instead of eth0 but I still get the same error: ... glibtop: netload: en0 : Undefined error: 0 Segmentation fault ... After reading the documentation on glibtop the last error made sense, but en0 seems like it should be a valid request. Any idea why glibtop doesn't like it? Is this a bug in the glib port? Oh, btw, I also wanted to say thanks to everyone thats been working on fink. It's an extremely useful tool. Job well done! Happy New Year to all, Jim ----------------------- Jim Beard Masters Student in CS @ U of Oregon http://www.cs.uoregon.edu/~jim |
From: Gordon M. <yi...@eb...> - 2001-12-30 17:09:15
|
Cool. I'm working on updating the qt package to 3.0.1, and have a quick try at activating qt threading for another app. On Sun, 30 Dec 2001, Jeff Whitaker wrote: > > I've just uploaded a new rev (9) of xfree86-base that patches darwin.cf > and Xos_r.h to activate threading. This allows some apps that require > threaded X11 libs to work (in my case, I was interested in cdat - > http://cdat.sf.net). It's been working fine for me for a few days of > heavy use - if anyone encounters any problems please let me know. > > -Jeff > > -- If I had a dollar for every brain that you don't have, I'd have one dollar. - Squidward to SpongeBob |
From: Jeff W. <js...@cd...> - 2001-12-30 16:44:50
|
I've just uploaded a new rev (9) of xfree86-base that patches darwin.cf and Xos_r.h to activate threading. This allows some apps that require threaded X11 libs to work (in my case, I was interested in cdat - http://cdat.sf.net). It's been working fine for me for a few days of heavy use - if anyone encounters any problems please let me know. -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 Meteorologist FAX : (303)497-6449 NOAA/OAR/CDC R/CDC1 Email : js...@cd... 325 Broadway Web : www.cdc.noaa.gov/~jsw Boulder, CO, USA 80303-3328 Office : Skaggs Research Cntr 1D-124 |
From: Gert D. <ge...@gr...> - 2001-12-30 16:41:04
|
Hi, On Sat, Dec 29, 2001 at 12:51:45PM -0800, Gordon Messmer wrote: > On Wed, 19 Dec 2001, Edwin C Wirth wrote: > > Is there a "communications package" installed? The usual ones (mincom, > > tip, cu, uucp, ...) are not, and I need to figure out how Darwin does > > tty device locking > > pppd is installed, and I suspect that you can check out the sources for it > from apple. How would one go about this? Or was this directed at Edwin? > The binary references /var/spool/lock, although the directory > doesn't exist by default. Hummm. /var/spool/lock is one of the usual places... > I suspect that locking is sorta neglected, since I can't see that locking > is done when I dial up over a modem on OS X. Ooops. What happens if you try to bring up PPP while being connected by modem to a BBS (or such)? Assuming that there *is* a terminal program for OS X in the first place... (Hmmm, what happens if you bring up a second PPP connection while a first one is occupying the modem? It has to figure this out, somehow) gert -- Gert Doering Mobile communications ... right now writing from *XMas Holiday* ... mobile phone: +49 177 2160221 ... or mail me: ge...@gr... |
From: Jim B. <be...@co...> - 2001-12-30 04:45:52
|
I've been trying to get a version of gkrellm up and running, but I'm not having much luck. The first hurdle I ran smack into was that the version of gkrellm that is in the unstable tree (1.2.1) is no longer distributed by it's author. Instead versions 1.2.4, 1.2.5 and 1.2.6 are available. I modified the .info and .patch file to point at a newer version ( I tried with 1.2.4 and 1.2.6 with exact same result.. ). This seemed to work fine. All of the object files for it compiled fine, however it died while linking them all together into the gkrellm binary. Here is the error I got: ... gcc -Wall -O2 -I.. `gtk-config --cflags gthread` `imlib-config --cflags-gdk` `libgtop-config --cflags` main.o alerts.o apm.o clock.o cpu.o disk.o fs.o hostname.o inet.o mail.o meminfo.o net.o proc.o sensors.o uptime.o chart.o panel.o config.o gui.o krell.o plugins.o utils.o -o gkrellm `gtk-config --libs gthread` `imlib-config --libs-gdk` `libgtop-config --libs` -lXau -Wl,-E /usr/bin/ld: unknown flag: -E make[1]: *** [gkrellm] Error 1 make: *** [gtop] Error 2 ### make failed, exit code 2 Failed: compiling gkrellm-1.2.4-1 failed ... So, it seemed like I was close, I dug through all the makefiles and the info/patch files trying to find out where the -E came from, but I couldn't find it. However I was able to run the command manually (omitting the -E) and get the binary to compile. The only problem being that it seg faults when I run it: ... [localhost:gkrellm-1.2.4-1/gkrellm-1.2.4/src] jim% ./gkrellm glibtop: netload: eth0 : Undefined error: 0 Segmentation fault ... I've recently done a fink selfupdate / fink update-all and got that latest glib stuff. I'm not sure where I should go from here. Any advice? Jim ----------------------- Jim Beard Masters Student in CS @ U of Oregon http://www.cs.uoregon.edu/~jim |
From: Daniel P. <da...@mw...> - 2001-12-29 22:27:29
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, December 29, 2001, at 04:33 AM, Jeff Whitaker wrote: > On Fri, 28 Dec 2001, Patrick Tescher wrote: > > Patrick: >> I am almost done with a evolution package and I have a problem. >> Evolution >> requires an older version of the db package, it cannot use the new >> version. >> This is a problem because: >> A) People may need the new package >> B) There is really no way of installing an older package > > Sure there is. fink install package-oldversion will install the old > package, replacing the newer version (package-newerversion). But only db 4 is in the Fink tree. Therefore, you can't install a newer version. >> So, my idea was to make a separate package called something like >> old_db that >> evolution requires. It could install in a separate folder. Anyone >> else have >> a better idea? I think db is designed so you can have more than one version installed at once. You should be able to install all of the libraries into /sw/lib, and AFAICT, installing includes into /sw/share/BerkeleyDB.<VERSION>/include/ or /sw/include/db#/ is common. (Looking at my MkLinux box.) Why don't you call it db3 or db2? Just my 2 cents. Daniel - -- PGP public key: http://mwdesign.dyndns.org/~daniel/publickey.txt ACA4 FA04 4033 0569 C626 AA1A C489 25A5 5F67 C125 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (Darwin) Comment: For info see http://www.gnupg.org iD8DBQE8LkNHxIklpV9nwSURAotVAKD1tVSc9x+Vb8x1rqpEUJLFtGyvWwCfeuks 9VL4oU0UgcfZ6Bu3vannCJc= =6rsz -----END PGP SIGNATURE----- |
From: Daniel P. <da...@mw...> - 2001-12-29 21:53:33
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I changed the subject to fit the new, more appropriate thread. On Thursday, December 27, 2001, at 03:37 AM, Max Horn wrote: > At 1:22 Uhr -0800 27.12.2001, Daniel Parks wrote: <snip> >> I already filed a feature request a while ago: >> http://sourceforge.net/tracker/?func=detail&atid=367203&aid=467764&group_id= >> 17203 >> >> Basically the response was "This isn't needed; use autoconf." > > That's nonsense, you can only use autoconf to change the build > process, but instead you want it to prevent installation. The end goal is the same. autoconf is used to turn features on and off depending on what software is already installed. Using OS dependencies disables the entire package if the correct OS is not installed. Of course, autoconf can be used to do this too -- Fink exits if ./configure returns something other than 0, right? (Yes, uname in a shell script could be used to do any of this too.) >> While I don't particularly like that solution (not all packages >> use autoconf; it's another thing to learn), I don't see a much >> better one ATM -- it would be essentially building an >> autoconf-like utility into Fink, and right now that's probably not >> worth the effort. > > Well, I think I like the idea Sylvain suggested. What do others > think about it? Thinking "out loud": It has the problem that Sylvain noted: how do you name packages? Personally, I would prefer to avoid having a bunch of name-osvers-pkgvers-rev packages. It's confusing, and it clutters up the list of packages. Furthermore, it allows package maintainers to create packages that only work on one OS. AFAIK, "official" policy is that Fink has binary support for 10.1.x, and (mostly?) has source support for 10.0.x. Fink should be coded to strongly encourage package maintainers to follow this policy. For these reasons I lean toward using autoconf or some other solution that changes the code to fit the OS. On the other hand, I wouldn't mind so much if we could hide all of those extra packages (e.g. bah-nox-darwin). See below. Next, there is the problem of binaries. Either way we go about this, we would have to release multiple binaries for the package in question, only support one OS version for that binary, or find some alternative way of dealing with the binary problem. Having separate packages for every possible condition helps here because each package has a unique name. (e.g. bah-nox-darwin, bah-darwin, bah- osx10.0-nox, bah-osx10.1, etc.) Using autconf means that it would be a PITA to support more than one OS version for binaries. I guess it really comes down to: do we want to have separate packages for each condition, or do we want to find a way of combining them all into one package. I think that we will encounter more problems like this in the future -- what happens when OS 10.2 comes out? And what if more people start using Fink on i386? And what about packages like GRASS (in the submission tracker, I AM working on it) which are highly modular -- I could create ten different GRASS-module packages, or I could just have one giant GRASS package with lots of dependencies. One possible way to support multiple packages in one is to create combo packages. Example: Package: grass Version: 5.0.0pre2 Revision: 2 Depends: g77, zlib, flex, bison, ncurses, x11, tcltk, libgl, libxpg4 (>= 20010605-7) Source: http://www.geog.uni- hannover.de/grass/grass5/source/grass%v_src.tar.gz SourceDirectory: grass%v . . . Module: postgresql [ Version: is optional here ] Revision: 1 Depends: postgresql, grass [ If grass isn't listed, than module postgresql is compiled before grass ] [ Source: is optional; defaults to GRASS source ] Then, you could request grass(all), or grass(postgresql gdal) or grass(none) or just grass, which would only build modules that already had their dependencies satisfied. I suppose what we really need is a more powerful and flexible syntax for .info files. Whew. Daniel - -- PGP public key: http://mwdesign.dyndns.org/~daniel/publickey.txt ACA4 FA04 4033 0569 C626 AA1A C489 25A5 5F67 C125 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (Darwin) Comment: For info see http://www.gnupg.org iD8DBQE8LjtTxIklpV9nwSURAlltAKCxckhn/F+iXMapN+18Qcj/TWfL9QCgthrR Bv1RbW2jrlOEmRF/q5SIl3I= =Nnqo -----END PGP SIGNATURE----- |
From: Gordon M. <yi...@eb...> - 2001-12-29 21:32:53
|
On Mon, 17 Dec 2001, Max Horn wrote: > At 11:57 Uhr -0500 17.12.2001, David R. Morrison wrote: > >Here's the deal. You compile library A.1, then library B.1, which > >thus depends on A.1.dylib. Later, you upgrade your fink .info > >file from A.1 to A.2, and do "fink reinstall A". Now anything which > >links to library B potentially has trouble, because "A.1.dylib" is > >hardcoded into B but only "A.2.dylib" now exists on your system. Does dpkg not deal with file dependencies? I've worked extensively with RPM (but not yet dpkg). When you build an rpm package, before the binaries are packed, dependencies are compiled. Some dependencies come out of the "spec" file, but rpm examines all of the files that are being packaged, and determines what files are required for *all* executable files. It checks scripts for the required interpereter, and examines binaries for their loader and libraries (using ldd). All of these things become dependencies. So, on an rpm system, you would be able to rebuild the "A" package, but if the new package had "A.2.dylib" and not "A.1.dylib", then attempting to actually upgrade the new "A" package would warn you that "B" requires "A.1.dylib". (It should also warn you about any other packages that are linked against "B", since those are also linked against "A"). rpm would allow you to install the package (not upgrade) as long as the new package and old package don't have file conflicts. You'd end up with two packages with the same name, but different versions, and different files installed. > So, this of course is still not nice to the user, I stumbled over > this several times, too... so what can we do about it: > > 1) Somehow keep the old revisions of the lib, parallel to the new, as > long as it is being used > > 2) Force a rebuild on depending packaged. > > > Regarding 1): This would mean we have to track all apps/packages > depending on that particular version of the .dylib, and keeping the > .dylib as long as any such application is still installed. The > problem here is that this would be quite hard to implement. How > should fink notice this dependency on a particular lib revision? What > if we later re-install a package that needs that particular .dylib > revision, after we have remove the old .dylib? I take that to mean that dpkg does not track file dependencies? That seems like a serious deficiency (and makes me wonder about all those Debian users telling me about the "technical superiority" of dpkg all these years). Looking at http://sistemac.carnet.hr/paketi/dpkg-full/ch-sharedlibs.html, it looks like dpkg *does* support this, but's it was terribly manual at the time. It's old documentation, and I can't find anything more recent. :( -- If I had a dollar for every brain that you don't have, I'd have one dollar. - Squidward to SpongeBob |
From: Gordon M. <yi...@eb...> - 2001-12-29 20:51:59
|
On Wed, 19 Dec 2001, Edwin C Wirth wrote: > Is there a "communications package" installed? The usual ones (mincom, > tip, cu, uucp, ...) are not, and I need to figure out how Darwin does > tty device locking pppd is installed, and I suspect that you can check out the sources for it from apple. The binary references /var/spool/lock, although the directory doesn't exist by default. I suspect that locking is sorta neglected, since I can't see that locking is done when I dial up over a modem on OS X. -- If I had a dollar for every brain that you don't have, I'd have one dollar. - Squidward to SpongeBob |
From: Finlay D. <fin...@bt...> - 2001-12-29 18:58:47
|
On Thursday, December 27, 2001, at 08:38 pm, Max Horn wrote: > I experimentally added the two pseudo packages to my local fink > repository, they seem to work well enough. > > I wonder if I should change the version of the "macosx" package to be > the build number instead of the system version? Like "5P48" instead of > "10.1.2" etc. > > What do you think about this, and about these two proposed pseudo > packages in general? My immediate reaction is that it's a bad idea, could you please justify? Also, build number is definitely a bad idea, because you can't rely on it (i.e. international versions might have different ones, taking into account the internal branches, etc). -- Finlay |
From: Jeff W. <js...@cd...> - 2001-12-29 12:32:34
|
On Fri, 28 Dec 2001, Patrick Tescher wrote: Patrick: > I am almost done with a evolution package and I have a problem. Evolution > requires an older version of the db package, it cannot use the new version. > This is a problem because: > A) People may need the new package > B) There is really no way of installing an older package Sure there is. fink install package-oldversion will install the old package, replacing the newer version (package-newerversion). > > So, my idea was to make a separate package called something like old_db that > evolution requires. It could install in a separate folder. Anyone else have > a better idea? > This should work. I don't know about having it in a separate folder though. You could just have the old_db package conflict, replace and provide db. That way, users who want evolution will just have to live with using the old package. We have something similar with tetex and ghostscript - tetex requires ghostscript6 with replaces the newer version of ghostscript if it is installed. Great work - I look forward to trying it out. -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 Meteorologist FAX : (303)497-6449 NOAA/OAR/CDC R/CDC1 Email : js...@cd... 325 Broadway Web : www.cdc.noaa.gov/~jsw Boulder, CO, USA 80303-3328 Office : Skaggs Research Cntr 1D-124 |
From: Patrick T. <pa...@ma...> - 2001-12-29 06:01:02
|
I am almost done with a evolution package and I have a problem. Evolution requires an older version of the db package, it cannot use the new version. This is a problem because: A) People may need the new package B) There is really no way of installing an older package So, my idea was to make a separate package called something like old_db that evolution requires. It could install in a separate folder. Anyone else have a better idea? |
From: Martin C. <cos...@wa...> - 2001-12-28 19:29:14
|
Max, in the new sawfish info file, there is a field "DoxFiles:". Is this a new feature of Fink? (just kidding...) In any case, the result is that the DocFiles are not copied into the package. -- Martin |
From: <ol...@fo...> - 2001-12-27 22:32:11
|
Am Donnerstag den, 27. Dezember 2001, um 23:01, schrieb Max Horn: > At 22:51 Uhr +0100 27.12.2001, Olaf F=F6llinger wrote: >> Hi, >> >> I was glad today finding the slrn package in he list of available=20 >> software. However it doesn't work here. I have build a version with=20= >> similar behaviour > > It would be much better if you would describe the "behaviour", instead=20= > of justing saying that it has the same. We can't read minds, nor do we=20= > have a magical scyring glass. Yes, you're right. The problem (no response to keyboard input) is so=20 evident that I've forgotten to mention it. > Anyway, maybe you mean the issues outlined at=20 > = https://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D471070&group= _id=3D > 17203&atid=3D117203 ? Yes. >> so I assume the version on the archives isn't linked against = termcap.=20 >> Is it right ? > > Hu? What do you mean with "not linked against termcap" ? The termcap=20= > functions are part of the system, nothing you link with. And the=20 > problem seems to be caused by a problem in/with the slang package. When I try to build the slrn package I get [merlin:~/projects/slrn-0.9.7.3] ergo% make . . . Making all in src cc -g -O2 -o chkslang chkslang.o ../intl/libintl.a -L/usr/local/lib=20= -lslang -ltermcap -lm /usr/bin/ld: can't locate file for: -ltermcap make[1]: *** [chkslang] Error 1 make: *** [all-recursive] Error 1 [merlin:~/projects/slrn-0.9.7.3] ergo% so I thought the problem might be related to a missing termcap library.=20= I'm not an expert in this area so I might hve missed the point. If it's a slang problem we might ask the deveopers of slrn. > >> If yes, how can we resolve this issue ? > > No idea. It's a pity. Greetings Olaf |
From: Max H. <ma...@qu...> - 2001-12-27 22:01:46
|
At 22:51 Uhr +0100 27.12.2001, Olaf F=F6llinger wrote: >Hi, > >I was glad today finding the slrn package in he list of available >software. However it doesn't work here. I have build a version with >similar behaviour It would be much better if you would describe the "behaviour", instead of justing saying that it has the same. We can't read minds, nor do we have a magical scyring glass. Anyway, maybe you mean the issues outlined at https://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D471070&group_i= d=3D17203&atid=3D117203 ? > so I assume the version on the archives isn't linked against >termcap. Is it right ? Hu? What do you mean with "not linked against termcap" ? The termcap functions are part of the system, nothing you link with. And the problem seems to be caused by a problem in/with the slang package. > If yes, how can we resolve this issue ? No idea. Max -- ----------------------------------------------- Max Horn Software Developer email: <mailto:ma...@qu...> phone: (+49) 6151-494890 |
From: <ol...@fo...> - 2001-12-27 21:51:46
|
Hi, I was glad today finding the slrn package in he list of available software. However it doesn't work here. I have build a version with similar behaviour so I assume the version on the archives isn't linked against termcap. Is it right ? If yes, how can we resolve this issue ? Greetings Olaf |
From: Sylvain C. <za...@no...> - 2001-12-27 21:50:05
|
Hi Max, I'm no unix guru so if you I have an idea for this error. What's weird is that during build a multiple definition is a=20 warning not an error. Moreover it's a conflict between 2 non-fink=20 librairies : usr/lib/libcrypto.0.9.dylib(fcrypt.o) &=20 = /System/Library/Frameworks/Kerberos.framework/Versions/A/Frameworks/Kerber= osDES. framework/Versions/A/KerberosDES(master.o) Zauc D=E9but du message r=E9exp=E9di=E9 : > De : "Alexander K. Hansen" <ha...@ps...> > Date : Jeu 27 d=E9c 2001 03:38:24 PM Europe/Paris > =C0 : Sylvain Cuaz <za...@no...> > Objet : R=E9p : Problem with CVS update -- CVS itself > > I have 10.1.2. > > On 12/26/01 5:58 PM, "Sylvain Cuaz" <za...@no...> wrote: > >> >> Le mercredi 26 d=E9cembre 2001, =E0 10:30 PM, Alexander K. Hansen a = =E9crit : >> >>> >>> su akhansen -c 'cvs -z3 update -d -P' >>> dyld: cvs multiple definitions of symbol _des_crypt >>> /usr/lib/libcrypto.0.9.dylib(fcrypt.o) definition of _des_crypt >>> = /System/Library/Frameworks/Kerberos.framework/Versions/A/Frameworks/Kerber= os >>> DES.framework/Versions/A/KerberosDES(master.o) definition of=20 >>> _des_crypt >>> ### su failed, exit code 66 >>> Failed: Updating using CVS failed. Check the error messages above. >>> [ldx3:~] akhansen% >> >> What's your system version ? MacOS X 10.1.1, if this is the case >> try updating to 10.1.2 because cvs was updated precisely to enable = its >> build on 10.1.2. >> >> BTW Max, is there a way to know on what we are building apart from >> uname wich only give the kernel version (in particular to know the >> version of MacOS X because the kernel don't necessarely change with >> every update of MacOS X). IIRC this was discussed before during the >> transition to 10.1 but I can't find where. Perhaps a bundle in the = base >> files, so as to be able to specify : >> Depends: osx (>=3D10.1.2) >> or >> Depends: darwin (>=3D5.2) >> with darwin being installed on both pure darwin and osx, and osx only >> installed on osx =3D) >> >> But there's another problem which version to support, just 10.1.2 or >> both ? and secondly how : cvs-10.1.2-1.11-2.info and >> cvs-10.1.1-1.11-2.info argh that's no good. >> >> I will think about it and maybe file a feature request if my >> thoughts get clearer. >> >> >>> >>> That'll teach me to use unstable packages! Has anybody gotten >>> cvs_1.11-2 to >>> work for them? >> >> >> I just try selfupdate and that worked well for me, but I'm under >> 10.1.2. >> >> >> Zauc >> >> > > -- > Alexander K. Hansen > Associate Research Scientist, Columbia University, LDX Collaboration > MIT Plasma Science and Fusion Center, 175 Albany Street, NW17-219 > Cambridge, MA 02139-4213 > Phone: 617-252-1818 Fax: 208-988-4057 > > |
From: Sylvain C. <za...@no...> - 2001-12-27 21:34:11
|
Le jeudi 27 d=E9cembre 2001, =E0 09:38 PM, Max Horn a =E9crit : > I experimentally added the two pseudo packages to my local fink=20 > repository, they seem to work well enough. cool > I wonder if I should change the version of the "macosx" package to be=20= > the build number instead of the system version? Like "5P48" instead of=20= > "10.1.2" etc. well, build number is only useful for specifying a system that = does=20 not have a version, ie for inter-release builds. Moreover version number (10.1.2) is more "human-readable" and = easy=20 to remember. Or perhaps we could use both : - v10.1.2 - b5P48 > What do you think about this, and about these two proposed pseudo=20 > packages in general? I (being the proposer) think they're very good =3D) =3D) Zauc |
From: Max H. <ma...@qu...> - 2001-12-27 20:54:22
|
I experimentally added the two pseudo packages to my local fink repository, they seem to work well enough. I wonder if I should change the version of the "macosx" package to be the build number instead of the system version? Like "5P48" instead of "10.1.2" etc. What do you think about this, and about these two proposed pseudo packages in general? Max -- ----------------------------------------------- Max Horn Software Developer email: <mailto:ma...@qu...> phone: (+49) 6151-494890 |
From: Max H. <ma...@qu...> - 2001-12-27 17:50:03
|
I just found out how to do that by modifying my termcap file. Shortly after I did this, I found at least one person did it before me (could have saved me some time to find out earlier :) http://www.kung-foo.tv/termcap.html Max -- ----------------------------------------------- Max Horn Software Developer email: <mailto:ma...@qu...> phone: (+49) 6151-494890 |