Re: gdselect alpha 3
Hmm, I think this is my first comment on this.. On Thu, 15 Oct 1998, Tom Lees wrote: On Wed, Oct 14, 1998 at 02:29:04PM -0700, Joey Hess wrote: Are there any plans to merge this with apt? Seems gdselect has the frontend, and apt has the backend. Well, I could do with some apt in-built dependency handling :) There isnt time before the freeze, and AFAIK there are no plans now (which means there are no plans now). I think this idea of 'lets quickly do something fast' is ill concieved and is ultimately going to hurt our image. I've looked at the latest version, it looks rather pretty, it's slightly more functional than dselect but that's about it.. It doesn't support any of the more sophisticated things that people are clamoring for, and it requires X, GTK and a wack of ram. The fact that it doesn't use the APT library only makes things worse as now it could have big bugs in odd places! Only problem is, apt is in C++, this is in C... So compile your code as C++, it's not hard, change the gcc call to g++ and rename the source files. Then you have to fix up a couple casts and some other things and presto, it's C++. You don't need to use gtk-- or anything else like that. Everything else is done, and I'm adding more UI features. In alpha3? Quick IRC survey shows that it locked one persons machine hard, takes huge amounts of ram+time and has randomly segfaulted for another... I belive Adam Heath has been investigating porting gdselect to libapt, perhaps you should talk to him. Jason
Re: gdselect alpha 3
Quoting Jason Gunthorpe ([EMAIL PROTECTED]): I think this idea of 'lets quickly do something fast' is ill concieved and is ultimately going to hurt our image. I've looked at the latest version, it looks rather pretty, it's slightly more functional than dselect but that's about it.. It doesn't support any of the more sophisticated things that people are clamoring for, and it requires X, GTK and a wack of ram. But it answers the people who think dselect is ugly and unintuitive and want something that runs under X. Perhaps an incremental approach is good: a good gui for the existing product in this release, other features in other releases. Maybe apt will be better, but we haven't seen it yet (referring to the UI). Apt's been in development for a long time, maybe some friendly competition will help. And why can't we have multiple UI's to the package management system? This is linux: one size doesn't fit all. Mike Stone
Re: gdselect alpha 3
Hi, Michael == Michael Stone [EMAIL PROTECTED] writes: Michael Quoting Jason Gunthorpe ([EMAIL PROTECTED]): I think this idea of 'lets quickly do something fast' is ill concieved and is ultimately going to hurt our image. I've looked at the latest version, it looks rather pretty, it's slightly more functional than dselect but that's about it.. It doesn't support any of the more sophisticated things that people are clamoring for, and it requires X, GTK and a wack of ram. Michael But it answers the people who think dselect is ugly and Michael unintuitive and want something that runs under X. A quick and dirty answers is not really a good thing, don't you think? Michael Perhaps an incremental approach is good: a good gui for the Michael existing product in this release, other features in other Michael releases. Maybe apt will be better, but we haven't seen it Michael yet (referring to the UI). Apt's been in development for a Michael long time, maybe some friendly competition will help. And Michael why can't we have multiple UI's to the package management Michael system? This is linux: one size doesn't fit all. Competition is fine, let it get time to mature. The idea is simple: no new code after freeze. let this new system vie with apt at the next release. Since when have we considered scrapping quality just because people want something that ``looks pretty''? manoj -- I have never seen anything fill up a vacuum so fast and still suck. Rob Pike, on X. Steve Jobs said two years ago that X is brain-damaged and it will be gone in two years. He was half right. Dennis Ritchie Dennis Ritchie is twice as bright as Steve Jobs, and only half wrong. Jim Gettys Manoj Srivastava [EMAIL PROTECTED] http://www.datasync.com/%7Esrivasta/ Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
Re: gdselect alpha 3
On Thu, Oct 15, 1998 at 05:52:59PM -0600, Jason Gunthorpe wrote: Hmm, I think this is my first comment on this.. On Thu, 15 Oct 1998, Tom Lees wrote: On Wed, Oct 14, 1998 at 02:29:04PM -0700, Joey Hess wrote: Are there any plans to merge this with apt? Seems gdselect has the frontend, and apt has the backend. Well, I could do with some apt in-built dependency handling :) There isnt time before the freeze, and AFAIK there are no plans now (which means there are no plans now). I think this idea of 'lets quickly do something fast' is ill concieved and is ultimately going to hurt our image. I've looked at the latest version, it looks rather pretty, it's slightly more functional than dselect but that's about it.. It doesn't support any of the more sophisticated things that people are clamoring for, and it requires X, GTK and a wack of ram. But, it does answer an immediate need... dselect is now too unwieldy to use with the number of packages we have... apt is not ready. Compare it with the package pre-selections in hamm. They were quick and dirty, but they worked, and I believe they helped a lot of users in installation (they were useful last time I used them). The only idea is not lets quickly do something fast. I started playing around with a simple package browser about a month ago... that's where the base came from. Converting it into a fully-blown package selector is what I decided to do. The fact that it doesn't use the APT library only makes things worse as now it could have big bugs in odd places! ^^ Probably does have... but then APT isnt perfect either. I think the point is APT has had much more debugging, this hasn't. I agree, but I needed something to get it up off the ground quickly. It could now almost certainly be ported to libapt very quickly, whereas writing it to libapt in the first place would have been harder, especially considering I already had the basics done a while ago. Only problem is, apt is in C++, this is in C... So compile your code as C++, it's not hard, change the gcc call to g++ and rename the source files. Then you have to fix up a couple casts and some other things and presto, it's C++. You don't need to use gtk-- or anything else like that. Oh. In that case, I will redirect my efforts to this. Everything else is done, and I'm adding more UI features. In alpha3? Quick IRC survey shows that it locked one persons machine hard, takes huge amounts of ram+time and has randomly segfaulted for another... AFAIK, UI features aren't what cause these - its my q+d package lib. The UI features are very quick, IMHO cleanly coded, and I thought them out a lot. I also need to run it through a malloc debugger soon to check out some possible memory leaks/boundary probs. I belive Adam Heath has been investigating porting gdselect to libapt, perhaps you should talk to him. OK, good idea (he's CCd)... Adam, how far have you got? Maybe we should collaborate on this. I believe its probably not much effort to port to libapt - the main problem is the dependency screen bit. -- Tom Lees [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.lpsg.demon.co.uk/ PGP Key: finger [EMAIL PROTECTED], http://www.lpsg.demon.co.uk/pgpkeys.asc.
Re: gdselect alpha 3
Quoting Manoj Srivastava ([EMAIL PROTECTED]): Michael == Michael Stone [EMAIL PROTECTED] writes: Michael Quoting Jason Gunthorpe ([EMAIL PROTECTED]): I think this idea of 'lets quickly do something fast' is ill concieved and is ultimately going to hurt our image. I've looked at the latest version, it looks rather pretty, it's slightly more functional than dselect but that's about it.. It doesn't support any of the more sophisticated things that people are clamoring for, and it requires X, GTK and a wack of ram. [snip] Michael Perhaps an incremental approach is good: a good gui for the Michael existing product in this release, other features in other Michael releases. Maybe apt will be better, but we haven't seen it Michael yet (referring to the UI). Apt's been in development for a Michael long time, maybe some friendly competition will help. And Michael why can't we have multiple UI's to the package management Michael system? This is linux: one size doesn't fit all. Competition is fine, let it get time to mature. The idea is simple: no new code after freeze. let this new system vie with apt at the next release. I didn't mean to argue that gdselect should necessarily ship now; by release I meant this release of gdselect. What I was trying to answer was an attitude that seemed to be saying we shouldn't do anything about dselect until we have a solution that not only provides a decent gui, but also everything else. (Which I took to mean automatic package dselection, superpackages, seamless x/tty transition, and everything else that apt is supposed to provide.) Some people just want a gui, and I think it's reasonable to provide it. It's not fair to compare gdselect with what apt is supposed to be, if for no other reason than that they're not trying to acheive the same goals. BTW, since I don't see how gdselect could be used on initial installation anyway, I don't think it would hurt to leave it off the cd's and make it available for download later. We can call it a beta or whatever, but those who want it could still use it. Mike Stone
Re: gdselect alpha 3
On Fri, 16 Oct 1998, Michael Stone wrote: Michael Perhaps an incremental approach is good: a good gui for the Michael existing product in this release, other features in other Michael releases. Maybe apt will be better, but we haven't seen it Michael yet (referring to the UI). Apt's been in development for a Michael long time, maybe some friendly competition will help. And Michael why can't we have multiple UI's to the package management Michael system? This is linux: one size doesn't fit all. There was a feature on slashdot a while ago saying that projects that sit around and talk constantly never do anything. Ones that have someone just put up some code for the public to critique seem to be the fastest and the best. The code has been put up, now its our turn to suggest how it can be fixed/improved, not complain that it shouldn't be there at all. I didn't mean to argue that gdselect should necessarily ship now; by release I meant this release of gdselect. What I was trying to answer was an attitude that seemed to be saying we shouldn't do anything about dselect until we have a solution that not only provides a decent gui, but also everything else. (Which I took to mean automatic package dselection, superpackages, seamless x/tty transition, and everything else that apt is supposed to provide.) Some people just want a gui, and I think it's reasonable to provide it. It's not fair to compare gdselect with what apt is supposed to be, if for no other reason than that they're not trying to acheive the same goals. Perhaps this can encourage the apt maintainers to finalize how the different ui's interface with their libraries in a universal way. Since all they have had is the CLI, there may be some work to finish for this. BTW, since I don't see how gdselect could be used on initial installation anyway, I don't think it would hurt to leave it off the cd's and make it available for download later. We can call it a beta or whatever, but those who want it could still use it. I think sid is the place for this. When you are ready, you can move it to the current unstable. Brandon P.S. just looking at the screen shots, I think this is a really good thing. Bravo. --+-- Brandon Mitchell [EMAIL PROTECTED] | Debian Testing Group Status PGP Key: finger -l [EMAIL PROTECTED] | http://bhmit1.home.ml.org/deb/ Dijkstra probably hates me (Linus Torvalds, in kernel/sched.c)
Re: gdselect alpha 3
Manoj Srivastava wrote: Hi, Michael == Michael Stone [EMAIL PROTECTED] writes: Michael Quoting Jason Gunthorpe ([EMAIL PROTECTED]): I think this idea of 'lets quickly do something fast' is ill concieved an d is ultimately going to hurt our image. I've looked at the latest version, it looks rather pretty, it's slightly more functional than dselect but that's about it.. It doesn't support any of the more sophisticated things that people are clamoring for, and it requires X, GTK and a wack of ram. Michael But it answers the people who think dselect is ugly and Michael unintuitive and want something that runs under X. A quick and dirty answers is not really a good thing, don't you think? Competition is fine, let it get time to mature. The idea is simple: no new code after freeze. let this new system vie with apt at the next release. Since when have we considered scrapping quality just because people want something that ``looks pretty''? manoj If it's rather pretty and slightly more functional than dselect but that's about it... then include it! Please! What I need from dselect is more screen space, more pixels, a less crampled selection environment. It takes forver to navigate through dselect because of the sheer number of packages. It seems that gdselect would help a lot in this respect (I use 1600x1200 on X). -- Peter Galbraith, research scientist [EMAIL PROTECTED] Maurice Lamontagne Institute, Department of Fisheries and Oceans Canada P.O. Box 1000, Mont-Joli Qc, G5H 3Z4 Canada. 418-775-0852 FAX: 775-0546 6623'rd GNU/Linux user at the Counter - http://counter.li.org/
Re: gdselect alpha 3
On Fri, Oct 16, 1998 at 09:48:18AM -0400, Peter S Galbraith wrote: Manoj Srivastava wrote: Hi, Michael == Michael Stone [EMAIL PROTECTED] writes: Michael Quoting Jason Gunthorpe ([EMAIL PROTECTED]): I think this idea of 'lets quickly do something fast' is ill concieved an d is ultimately going to hurt our image. I've looked at the latest version, it looks rather pretty, it's slightly more functional than dselect but that's about it.. It doesn't support any of the more sophisticated things that people are clamoring for, and it requires X, GTK and a wack of ram. Michael But it answers the people who think dselect is ugly and Michael unintuitive and want something that runs under X. A quick and dirty answers is not really a good thing, don't you think? Competition is fine, let it get time to mature. The idea is simple: no new code after freeze. let this new system vie with apt at the next release. Since when have we considered scrapping quality just because people want something that ``looks pretty''? manoj If it's rather pretty and slightly more functional than dselect but that's about it... then include it! Please! What I need from dselect is more screen space, more pixels, a less crampled selection environment. It takes forver to navigate through dselect because of the sheer number of packages. It seems that gdselect would help a lot in this respect (I use 1600x1200 on X). So... shall I release it using my pkg code (takes lots of memory, blah, blah, blah, but it works, and its written), or apt's class system? I now think its too silly to try to include it in the slink freeze; I will upload it to unstable after the freeze has happenned. However, making a note of it on the Debian web pages might not be such a bad idea. -- Tom Lees [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.lpsg.demon.co.uk/ PGP Key: finger [EMAIL PROTECTED], http://www.lpsg.demon.co.uk/pgpkeys.asc.
Re: gdselect alpha 3
On Fri, 16 Oct 1998, Tom Lees wrote: Adam, how far have you got? Maybe we should collaborate on this. I believe its probably not much effort to port to libapt - the main problem is the dependency screen bit. Well, I removed the dpkg.a file, and started rem'ing out code. Got that to compile, and then added the libapt init stuff. That is as far as I got. Also, to get gdselect to run as root, I had to patch to lines, as follows. -- before while (!dpkg_lock(/var/lib/dpkg)) if ((yesnobox (Error locking database; correct data cannot be re-read; retry?)==0)) return; -- after while (dpkg_lock(/var/lib/dpkg)) if ((yesnobox (Error locking database; correct data cannot be re-read; retry?)==0)) return; -- Without doing this, gdselect would be able to 'lock' the db, and run as a normal user, but not as root. Also, dselect still reads the db, and allows a normal user to browse the list, but keeps them from making any changes. Currently, gdselect doesn't allow this. Adam
Re: gdselect alpha 3
On Fri, 16 Oct 1998, Tom Lees wrote: I agree, but I needed something to get it up off the ground quickly. It could now almost certainly be ported to libapt very quickly, whereas writing it to libapt in the first place would have been harder, especially considering I already had the basics done a while ago. Well depending on how you wrote things you might find that libapt is 'hard' to port too. Adam, how far have you got? Maybe we should collaborate on this. I believe its probably not much effort to port to libapt - the main problem is the dependency screen bit. Well, if we are going to try for this I guess we ought to move over to the deity list.. The library source and such forth is in CVS as usual. There is a new forked development tree called 'apt' which is distinct and very different from the current release. To get it do something like export CVSROOT=:pserver:[EMAIL PROTECTED]:/cvs/deity cvs login cvs co apt cd apt aclocal -I buildlib autoconf mkdir build cd build ../configure make You'll need g++ and libstdc++2.9. To make use of the library from your program you'll want to include -L .../apt/build/lib and -I .../apt/build/include and use -lapt-pkg Then you can start working on removing your library and replacing it with this one.. I guess the main areas of questioning would be something like 1) How do I startup the library 2) How do I get a list of packages - Packages that a package depends on - With some sort of filter criteria 3) How do I install/remove/keep a package I guess I'll write another mail outlining the basic elements of each of these. Jason
Re: gdselect alpha 3
On Fri, Oct 16, 1998 at 09:48:18AM -0400, Peter S Galbraith wrote: What I need from dselect is more screen space, more pixels, a less crampled selection environment. It takes forver to navigate through dselect because of the sheer number of packages. It seems that gdselect would help a lot in this respect (I use 1600x1200 on X). I run 640x480 or 800x600 depending. I want gdselect ported back to console. = pgpZL1q31i2og.pgp Description: PGP signature
Re: Screenshots (Re: gdselect alpha 3)
Nils Rennebarth wrote: On Wed, Oct 14, 1998 at 05:03:22PM +0200, Martin Schulze wrote: I was told recently that people might be interested in some screenshots of the program. The following page contains three images. http://www.infodrom.north.de/~joey/Linux/Debian/gdselect.html Does anyone else has the problem of netscape 4.07 segfaulting on the second and third screenshot? Args. I've not converted them into .jpg. This increases their size up to 100kB. I thought .jpg would contain compression. Regards, Joey -- Install joe (Joey's Own Editor) correct: Joe's Own Editor
Re: Screenshots (Re: gdselect alpha 3)
Martin Schulze wrote: Nils Rennebarth wrote: On Wed, Oct 14, 1998 at 05:03:22PM +0200, Martin Schulze wrote: I was told recently that people might be interested in some screenshots of the program. The following page contains three images. http://www.infodrom.north.de/~joey/Linux/Debian/gdselect.html Does anyone else has the problem of netscape 4.07 segfaulting on the second and third screenshot? Args. I've not converted them into .jpg. This increases their size up to 100kB. I thought .jpg would contain compression. JPEG is compression based on the change in value from one pixel to the surounding ones. This is better for photography than graphic art. Fast color change wrecks the compression... -- What do you want to spend today? Debian GNU/Linux (Free for an UNLIMITED time) http://www.debian.org/social_contract.html Greg VenceKH2EA/4
Re: Screenshots (Re: gdselect alpha 3)
On Wed, Oct 14, 1998 at 05:03:22PM +0200, Martin Schulze wrote: I was told recently that people might be interested in some screenshots of the program. The following page contains three images. http://www.infodrom.north.de/~joey/Linux/Debian/gdselect.html Does anyone else has the problem of netscape 4.07 segfaulting on the second and third screenshot? Nils -- *-* | Quotes from the net: L Linus Torvalds, W Winfried Truemper | | Lthis is the special easter release of linux, more mundanely called 1.3.84 | | WUmh, oh. What do you mean by special easter release?. Will it quit | * Wworking today and rise on easter? * pgpVbcNhdCN8u.pgp Description: PGP signature
Re: gdselect alpha 3
On Wed, Oct 14, 1998 at 02:29:04PM -0700, Joey Hess wrote: Are there any plans to merge this with apt? Seems gdselect has the frontend, and apt has the backend. Well, I could do with some apt in-built dependency handling :) There isnt time before the freeze, and AFAIK there are no plans now (which means there are no plans now). Only problem is, apt is in C++, this is in C... ATM, I'm struggling with getting dependencies with virtual packages and or (i.e. a | b | c, d) working (any chance of some help?). Everything else is done, and I'm adding more UI features. -- Tom Lees [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.lpsg.demon.co.uk/ PGP Key: finger [EMAIL PROTECTED], http://www.lpsg.demon.co.uk/pgpkeys.asc.
Re: gdselect alpha 3
Ben Gertzfield [EMAIL PROTECTED] writes: Martin == Martin Schulze [EMAIL PROTECTED] writes: Martin Fixed by moving #include stdio.h five lines up. I Martin fixed it but forget about it, since it was *that* easy. Martin Not even worth mentioning. Er, in which file? The file that errored out was deps.c and it doesn't even #include stdio.h.. Adding a #include stdio.h to it makes it compile. Quoting your original message: : In file included from deps.c:10: : /home/che/src/gdselect/gdselect-a3/include/dpkg-db.h:164: parse error before `FILE' ^^ Steve [EMAIL PROTECTED]
Screenshots (Re: gdselect alpha 3)
Hi, I was told recently that people might be interested in some screenshots of the program. The following page contains three images. http://www.infodrom.north.de/~joey/Linux/Debian/gdselect.html Regards, Joey -- Unix is user friendly ... It's just picky about it's friends.
Re: Screenshots (Re: gdselect alpha 3)
Le Wed, Oct 14, 1998 at 05:03:22PM +0200, Martin Schulze écrivait: http://www.infodrom.north.de/~joey/Linux/Debian/gdselect.html The startup image isn't available. But I have a problem with gdselect. The first time I ran it, i was logged in a non-root account. It worked and was able to browse through the package list. Now if I start gdselect as root, it doesn't work : Error locking database; correct data cannot be re-read; retry ? And I have to answer no. Does anybody know why i've got this error ? Cheers, -- Hertzog Raphaël ¤ 0C4CABF1 ¤ http://www.mygale.org/~hra/
Re: Screenshots (Re: gdselect alpha 3)
Raphael Hertzog wrote: Le Wed, Oct 14, 1998 at 05:03:22PM +0200, Martin Schulze écrivait: http://www.infodrom.north.de/~joey/Linux/Debian/gdselect.html The startup image isn't available. It is now. I'm too lame to type. Regards, Joey -- Unix is user friendly ... It's just picky about it's friends.
Re: gdselect alpha 3
On Tue, Oct 13, 1998 at 08:52:01PM +0200, Martin Schulze wrote: Tom Lees wrote: I released alpha 3 to http://www.lpsg.demon.co.uk/gdselect/ today. This looks quite impressive. Good work! One comment: On my system the gauge which is displayed first uses strange size. The y-stretch was about 5 times of the title bar. That looks ugly. I'd rather like it to be about 2 times of the y-stretch of the title bar (maybe three looks ok, too.) I really like the booting - dead impressive :-) When I started it from the wrong directory, it didn't load the picture (so the progress bar took up the entire window - is this what you mean? It'd be nice to sort the sections and packages into alphabetical order by default. Any chance of a .deb :- Adrian email: [EMAIL PROTECTED], http://www.poboxes.com/adrian.bridgett Windows NT - Unix in beta-testing. PGP key available on public key servers Avoid tiresome goat sacrifices -=- use Debian Linux http://www.debian.org
Re: gdselect alpha 3
Are there any plans to merge this with apt? Seems gdselect has the frontend, and apt has the backend. -- see shy jo
Re: gdselect alpha 3
Tom Lees wrote: I released alpha 3 to http://www.lpsg.demon.co.uk/gdselect/ today. This looks quite impressive. Good work! One comment: On my system the gauge which is displayed first uses strange size. The y-stretch was about 5 times of the title bar. That looks ugly. I'd rather like it to be about 2 times of the y-stretch of the title bar (maybe three looks ok, too.) Here's another comment: CQ does teh cursor turn into captain blue eyes when you're in teh window? :) ^- Nils Lohner Regards, Joey -- Experience is a useful thing. Unfortunately it is only acquired just after one could have used it.
Re: gdselect alpha 3
Tom == Tom Lees [EMAIL PROTECTED] writes: Tom I released alpha 3 to http://www.lpsg.demon.co.uk/gdselect/ Tom today. The next release will have all features present. This Tom is primarily a last testing phase. I cannot get alpha 3 to compile. (snip) gcc -g -Wall -Werror -I/home/che/src/gdselect/gdselect-a3/include -I/usr/X11R6/include -I/usr/lib/glib/include -c util.c -o util.o gcc -g -Wall -Werror -I/home/che/src/gdselect/gdselect-a3/include -I/usr/X11R6/include -I/usr/lib/glib/include -c deps.c -o deps.o In file included from deps.c:10: /home/che/src/gdselect/gdselect-a3/include/dpkg-db.h:164: parse error before `FILE' /home/che/src/gdselect/gdselect-a3/include/dpkg-db.h:165: parse error before `FILE' make[1]: *** [deps.o] Error 1 make[1]: Leaving directory `/home/che/src/gdselect/gdselect-a3/gtk' make: *** [all-subdirs] Error 2 I have GTK+ 1.1 and GLib 1.1 and their -devs installed. This is with GCC 2.7.2.3. -- Brought to you by the letters A and C and the number 5. Porco ga daisuki! -- Fio, Porco Rosso Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: gdselect alpha 3
Ben Gertzfield wrote: I cannot get alpha 3 to compile. (snip) gcc -g -Wall -Werror -I/home/che/src/gdselect/gdselect-a3/include -I/usr/X11R6/include -I/usr/lib/glib/include -c util.c -o util.o gcc -g -Wall -Werror -I/home/che/src/gdselect/gdselect-a3/include -I/usr/X11R6/include -I/usr/lib/glib/include -c deps.c -o deps.o In file included from deps.c:10: /home/che/src/gdselect/gdselect-a3/include/dpkg-db.h:164: parse error before `FILE' /home/che/src/gdselect/gdselect-a3/include/dpkg-db.h:165: parse error before `FILE' make[1]: *** [deps.o] Error 1 make[1]: Leaving directory `/home/che/src/gdselect/gdselect-a3/gtk' make: *** [all-subdirs] Error 2 I have GTK+ 1.1 and GLib 1.1 and their -devs installed. This is with GCC 2.7.2.3. Fixed by moving #include stdio.h five lines up. I fixed it but forget about it, since it was *that* easy. Not even worth mentioning. Regards, Joey -- Experience is a useful thing. Unfortunately it is only acquired just after one could have used it.
Re: gdselect alpha 3
Martin == Martin Schulze [EMAIL PROTECTED] writes: Martin Fixed by moving #include stdio.h five lines up. I Martin fixed it but forget about it, since it was *that* easy. Martin Not even worth mentioning. Er, in which file? The file that errored out was deps.c and it doesn't even #include stdio.h.. Adding a #include stdio.h to it makes it compile. -- Brought to you by the letters O and M and the number 2. Step away from the car. This car is protected by Viper. -- TMBG Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: gdselect alpha 3
Ben Gertzfield wrote: Martin == Martin Schulze [EMAIL PROTECTED] writes: Martin Fixed by moving #include stdio.h five lines up. I Martin fixed it but forget about it, since it was *that* easy. Martin Not even worth mentioning. Er, in which file? The file that errored out was deps.c and it doesn't even #include stdio.h.. Adding a #include stdio.h to it makes it compile. It did not? I'm sure mine did and I only moved it before the offending lines. Regards, Joey -- Experience is a useful thing. Unfortunately it is only acquired just after one could have used it.
Re: gdselect alpha 3
BG == Ben Gertzfield [EMAIL PROTECTED] writes: Martin == Martin Schulze [EMAIL PROTECTED] writes: Martin Fixed by moving #include stdio.h five lines up. I Martin fixed it but forget about it, since it was *that* easy. Martin Not even worth mentioning. BG Er, in which file? The file that errored out was deps.c and it doesn't BG even #include stdio.h.. Adding a #include stdio.h to it makes it BG compile. I moved it some line to the top in include/dpkg-db.h Ciao, Martin
Re: gdselect alpha 3
Martin == Martin Schulze [EMAIL PROTECTED] writes:
Martin Fixed by moving #include stdio.h five lines up. I
Martin fixed it but forget about it, since it was *that* easy.
Martin Not even worth mentioning.
Ben Er, in which file? The file that errored out was deps.c and
Ben it doesn't even #include stdio.h.. Adding a #include
Ben stdio.h to it makes it compile.
Martin It did not? I'm sure mine did and I only moved it before
Martin the offending lines.
Args, since it confuses so many people here's the patch. It was
probably a different file. Somebody needs to learn about reading
gcc errors...
--- include/dpkg-db.h.orig Wed Oct 14 00:10:56 1998
+++ include/dpkg-db.h Wed Oct 14 00:11:14 1998
@@ -158,6 +158,8 @@
extern void dpkg_free_avail (struct dpkg_tagpkg **pl);
extern void dpkg_free_status (struct dpkg_tagpkg **pl);
+#include stdio.h
+
/* misc.c */
extern int dpkg_lock (char *dir);
extern void dpkg_unlock (void);
@@ -165,8 +167,6 @@
extern void dpkg_write_select (struct dpkg_tagpkg *pl, FILE *f);
/* File: dpkg/db/tags.h */
-
-#include stdio.h
struct tagfile_tag
{
Regards,
Joey
--
Experience is a useful thing. Unfortunately it is only acquired
just after one could have used it.
