Re: KDE debs building
Yenar Calentaure wrote: Anyway, i did cvsup today and i am going to build packages. It is quite probable that i'll be able to upload them next week. I'll try to publish them through http, so they can be pulled by you (this will be probably the best solution for me). Beware: the line is synchronous 128kb AFAIK (or 128/64 in worst case), so download speed won't be very impressive :(. Oops... I broke it somehow (dcop isn't working)... I'll take a look at it (i see no dcop commits lately that could break it). Probably my qt-copy packaging broke something (it is unlikely but i possible). I'll cvsup once more and will try to get working debs in coming week. -- --- inetname: Yenar Calentaure realname: Peter Rockai mail: yenar(at)host.sk homepage: http://yenar.host.sk --- The universe is entering maintenance mode in 2 minutes. Please logout. -- Your administrator ---
Re: KDE debs building
Ralf Nolden wrote: On Monday 16 September 2002 17:25, Yenar Calentaure wrote: I have enough C++ experience to fix (or workaround at least) most common problems. There are little chances to get cvsup in middle of week for me unfortunately. Well, in that case I'd prefer sending you the according build files per email that the developers checked in to make it compile again. Even though you can fix issues yourself, you'll never know how it ends up in the real code comitted to CVS later. We'll find a solution to that problem in case we'll hit it, I guess. If compilation breaks and i find solution, i usually send patches to kde-devel. Sure, I don't know what will maintainer do, but it is still better to have slightly broken packages than having no packages at all :). As of sending updates to me by mail... I don't know if this is usable. It is hard to get right revisions to diff, and time of update isn't relevant (there are mirror sync, cvsup - cvs and probably other issues). It is probably easier to get cvsup working on weekdays for me. Anyway, i did cvsup today and i am going to build packages. It is quite probable that i'll be able to upload them next week. I'll try to publish them through http, so they can be pulled by you (this will be probably the best solution for me). Beware: the line is synchronous 128kb AFAIK (or 128/64 in worst case), so download speed won't be very impressive :(. I don't know if my last mail made it into your mailbox (the perl filter script) - i had some trouble with mozilla mail (i'm mailing from windoze box... this is very unfortunate). I ran into one problem with the script though. In KDE, binaries have two parts: /usr/bin binary and /usr/lib .so file. The kdelibs-bin includes (as expected) both for every app. This means i cannot filter on /usr/bin to get file-list for such package. Probably the best solution is to enumerate binary file names (as in (?:bin1|bin2|binx)). It will be handy to allow variable substitution in filter control file. Is there any standard way of definining such variables inside of control file? If not, is something like Var-(varname): blah acceptable? This means all leading/trailing whitespace will be trimmed from variable. cheers yenar - -- We're not a company, we just produce better code at less costs. - Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -- --- inetname: Yenar Calentaure realname: Peter Rockai mail: yenar(at)host.sk homepage: http://yenar.host.sk --- The universe is entering maintenance mode in 2 minutes. Please logout. -- Your administrator ---
Re: KDE debs building
On Monday 16 September 2002 16:07, Ralf Nolden wrote: On Monday 16 September 2002 17:00, you wrote: Ralf Nolden wrote: On Monday 16 September 2002 15:08, peter rockai wrote: Fine, that would help. I've unstable here, so we would have two builds for debian, which is what everyone needs. My builds include having XFree 4.2.1 installed, if that is a requirement for the linking I guess, we should note that these packages only work with XFree 4.2.1. I would even go as far as mirroring the XFree 4.2.1 packages on ftp.kde.org :-) They will depend on them, I'd guess (dh_shlibdeps). Btw., is it possible to apt-get from ftp.kde.org? I build full apt-get repo (only missing release file atm). Then it would be as easy as adding ftp.kde.org into your sources list and apt-get update/install/upgrade. Don't know about the breakage when packages get renamed (as with arts last week :). That would be fine. We would need someone to set up the apt-get system on ftp.kde.org for us. It would be really helpful if the apt-get tree would explicitly mention for what debain and kde version the deb are. debian/woody/kde-3.0.x kde-3.1.x (including alpha/beta) kde-cvs - kde-3.1.x (when a KDE_3_1_BRANCH is created (a kde-3.2.x subtree) kde-stable - kde-3.0.x debian/sid/(same subdir/links as above) IMHO one should keeping at least the last two kde-x.y.z tree so it's easy to test upgrades from kde-x.y.z to kde-u.v.w with just a s/x.y.x/u.v.w/ in sources.list. It would also be helpful if the debian pkg version contains the string woody or sid Last but not least a little 'reminder': there's a debian-pkg tree in kde cvs. Maybe it's useful as a central repository for 'debian' subdir in case upstream doesn't grant the deb package maintainer write access (or a new sf project, e.g. kde-debian-pkgs?) Just my two cent, Achim Dirk, Daniel, how is the status with the ftp server ? Can we get access to that ? I messed a bit with Xft2 but i'll clean up my system to build correct woody debs. I'll improve automation of my build system, so it will work alone as far as possible. Most problems with cvs are from compile breakage :(. That's the part that I would like to do; keep up constantly compiling here, too. You can't avoid breakage one over the other day sometimes, especially on weekends; just that the debian dirs are updated ASAP after developers did changes (I build kde from cvs anyway so I would keep that up) Atm i don't build all the stuff (i don't have always time to fix problems in packages like kdepim or kdeaddons). But i can provide at least qt-copy, kdelibs, kdebase and koffice weekly. Kdemultimedia breaks because of old xine atm (so i'm forced to use ogg123 instead of noatun kdemultimedia works for me. I have noatun there :-) :). I'll have to build xine-lib-cvs package, too, as i see it :). I used the unstable packages. ftp.kde.org will end up as experimental addon for debian ;). Yes, that is the goal here. I cvsup every weekend, so i could upload on monday afternoon. I really hope that it will be possible. But i'll need to drop them somewhere, so if you could provide me with ftp address and login/pass, i would be glad. Yes, we'll do that; even if I would offer my box with an account for you and I would collect everything here and put the packages back on ftp if Daniel and Dirk won't be willing to give away too many password accounts. Builts should be done tuesdays/wednesdays after a cvsup because weekend updates tend to be having problems with compilation until monday afternoon/tuesday morning GMT Btw., is there someone on the server who could untar if i uploaded one huge tarball? I'll try to get automated upload of multiple files working at school, but i can't promise anything :(. Dunno. Maybe Dirk or Daniel know more about that. Ralf - -- We're not a company, we just produce better code at less costs. - Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -- To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it. -- [EMAIL PROTECTED]
Re: KDE debs building
söndagen den 15 september 2002 17.35 skrev Ralf Nolden: as some of you got to know until now, I switched from SuSE to Debian this week - - and directly hit the fact that building debs from CVS would work best for me to have it working the right way (tm). Now, I got into working with Chris lately and we try to fix the issues one by one soon now so that everyone can build debs himself but more important, provide debs for KDE constantly that work, where also most importantly betas, RC's and finals are provided by the day that the packages are build and work optimal on Debian. I have some experience of packaging KDE into debs, and I think it would be great if we could combine our efforts. My KDE3.1-beta packaging was not originally meant for distribution to others, but it appears to be quite popular judging on the number of downloads I got (I have 123 downloads of kdelibs from my machine, and there are a mirrors), so I am thinking of making the packaging both better, more versatile and more fine-grained. My main interest is just something that works, and since the debian KDE packagers have announced that they are not interested in packaging KDE beta, and have said that they are starting their packaging efforts first when the final version is out, I aimed at packaging just beta versions and early releases. I don't think it is such a bad idea that the main packagers work on refining the final product, and are not bothered with beta versions when they come. Actually, what I really think is that by providing packaging of KDE betas, the packaging problems can be found at an early stage, making it much easier and less troublesome to fast provide a good final version for those who don't want surprises (like with libpng this spring). -- Karolina
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 15 September 2002 6:53 pm, Tamas Nagy wrote: Glad to hear the initiative. First of all, credit to all packagers, it was a good work... IMHO, the current practice (everybody creates own packaging for KDE) needs to be changed. The debian directories in CVS used to be outdated, and this leads to duplicated (and wasted) packaging efforts. KDE package building should be repeatable from the CVS by anyone. and they are for 3.0.x, see below for info. However there are some site, including mine (http://mypage.bluewin.ch/kde3-debian, for gathering all the (often incompatible) packages and sources ), the best would be to have a single repository for all the KDE Debian packages at ftp.kde.org. The problem is that several people are maintainers for several packages. Chris Cheney is maintainer for kdelibs, kdebase and others, while Ben Burton is maintainer for kdeartwork, kdeaddons, koffice and a few others. Someone else is maintainer for kdevelop. Finally, individual heroes, please try to use the KDE CVS (more frequently) and let everybody will benefit from your work. AFAIK, most people do use CVS and try to keep HEAD up to date. The problem there is that HEAD is a moving target. KDE developers add files, move files and remove files which means that the file lists in CVS are not up to date. Several people, including myself, build KDE HEAD as and when we can and update CVS so they are buildable, but we can't do all of the modules all of the time, so they won't always be buildable. BRANCH has pretty much been up to date since before 3.0.0 so people could build packages from CVS for the 3.0.x series. IMHO, the situation with KDE is significantly better than for most other Debian packages which do not have debian dirs available for development versions. Tamas -Original Message- From: Ralf Nolden [mailto:[EMAIL PROTECTED] Sent: Sunday, September 15, 2002 5:36 PM To: debian-kde@lists.debian.org Subject: KDE debs building Hi, as some of you got to know until now, I switched from SuSE to Debian this week - and directly hit the fact that building debs from CVS would work best for me to have it working the right way (tm). Now, I got into working with Chris lately and we try to fix the issues one by one soon now so that everyone can build debs himself but more important, provide debs for KDE constantly that work, where also most importantly betas, RC's and finals are provided by the day that the packages are build and work optimal on Debian. The other thing is that third party apps need to be compiled if you like to use them. Until now several people do that for the apps they like to run or that they are developing using debian as their development platform. The problem for the users is that the deb lines for sources.list are spread all over and there is no central way of getting the newest apps through debs for people that are not necessarily developers like we are. The other thing is that as developers, just doing a make install would work but that usually messes up our systems, especially as KDE has /usr as its prefix on debian. So it would be the best if we could somehow collect our resources and schedule building debs and providing them in a central place. I talked with Dirk Müller already and some other guys that I use to work with at KDE and we should provide that possibility through KDE on ftp.kde.org. Wether that will work out just depends on how many people would volunteer to participate. If you're interested, let's come together to finally end this messy system where there's certain problems with building debs for us and the KDE users using debian, it would surely make things a *lot* easier if we organize ourselves and coordinate doing things efficiently. Thanks for your attention and for volunteering :-) Ralf -- We're not a company, we just produce better code at less costs. Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9haDEYsCKa6wDNXYRAv3qAKCDLJFgZKFsfCFx00agVsZvchuUCQCdFyh8 OAl8hAvTFGBub6MSeJxbtgM= =Q9T1 -END PGP SIGNATURE-
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 15 September 2002 7:35 pm, Alan Chandler wrote: On Sunday 15 September 2002 4:35 pm, Ralf Nolden wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, as some of you got to know until now, I switched from SuSE to Debian this week - - and directly hit the fact that building debs from CVS would work best for me to have it working the right way (tm). Now, I got into working with Chris lately and we try to fix the issues one by one soon now so that everyone can build debs himself but more important, provide debs for KDE constantly that work, where also most importantly betas, RC's and finals are provided by the day that the packages are build and work optimal on Debian. Fantastic The other thing is that third party apps need to be compiled if you like to use them. Until now several people do that for the apps they like to run or that they are developing using debian as their development platform. The problem for the users is that the deb lines for sources.list are spread all over and there is no central way of getting the newest apps through debs for people that are not necessarily developers like we are. The other thing is that as developers, just doing a make install would work but that usually messes up our systems, especially as KDE has /usr as its prefix on debian. So it would be the best if we could somehow collect our resources and schedule building debs and providing them in a central place. Still not sure why KDE and these apps can't seem to make it into the formal debian unstable (and then the more stable) archive and mirrors, but apparently not - so ... Read the FAQ at http://www.davidpashley.com/debian-kde/faq.html I talked with Dirk Müller already and some other guys that I use to work with at KDE and we should provide that possibility through KDE on ftp.kde.org. Wether that will work out just depends on how many people would volunteer to participate. A good alternative - especially if you could set it up so that it had different sections for stable, unstable and development (or something) so that we could chose what. I am not sure how I could participate - I do have an always on, lightly used server supporting my family at home at the end of a cable modem, but my acceptable use conditions require that it is not used as a public server other than for a limited (10) password controlled connections. I could perhaps do some regular builds (Its only a p2 400 with 128MB Ram, but it has loads of disk space). As for my time, I am travelling abroad (from the UK) between 3 and 4 days a week, so that pretty much limits what I could do. I am trying to do some light coding or bug fixing offline in the evenings when I am away - but last weeks attempt was feeble, I managed only an hour (working late and then eating seems to grab most of the time). I could devote a bit more when I am at home. -- Alan Chandler [EMAIL PROTECTED] - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9haEZYsCKa6wDNXYRAh3+AJwIU5spgBSgKEUSYKp4t9pwJnaQ2ACfYq/n U+681Wq5w7iw11lw77GzmwE= =9FIJ -END PGP SIGNATURE-
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 5:53 am, Karolina Lindqvist wrote: söndagen den 15 september 2002 17.35 skrev Ralf Nolden: as some of you got to know until now, I switched from SuSE to Debian this week - - and directly hit the fact that building debs from CVS would work best for me to have it working the right way (tm). Now, I got into working with Chris lately and we try to fix the issues one by one soon now so that everyone can build debs himself but more important, provide debs for KDE constantly that work, where also most importantly betas, RC's and finals are provided by the day that the packages are build and work optimal on Debian. I have some experience of packaging KDE into debs, and I think it would be great if we could combine our efforts. My KDE3.1-beta packaging was not originally meant for distribution to others, but it appears to be quite popular judging on the number of downloads I got (I have 123 downloads of kdelibs from my machine, and there are a mirrors), so I am thinking of making the packaging both better, more versatile and more fine-grained. My main interest is just something that works, and since the debian KDE packagers have announced that they are not interested in packaging KDE beta, and have said that they are starting their packaging efforts first when the final version is out, I aimed at packaging just beta versions and early releases. I don't think it is such a bad idea that the main packagers work on refining the final product, and are not bothered with beta versions when they come. I'm sorry that just isn't true. KDE HEAD has been kept up to date as much as possible. People have been able to build packages for 3.1 for the last few months. I could check the dates if you are interested. We haven't provided binary packages because a) they take up a lot of room and b) calc has been busy making sure that 3.0.x is working, bab has been working on koffice 1.2 and everyone else has been making sure that HEAD works. We have never said that we will start for on 3.1 debs once 3.1 has been released. Actually, what I really think is that by providing packaging of KDE betas, the packaging problems can be found at an early stage, making it much easier and less troublesome to fast provide a good final version for those who don't want surprises (like with libpng this spring). -- Karolina - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9haJkYsCKa6wDNXYRAjpwAJ0V3DU+iLiUJwbm8pTiCdAZojSmQQCeI6i8 wjVyXZKAS5Jj5Cb49V9ejdY= =UVqw -END PGP SIGNATURE-
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 12:33 am, Ralf Nolden wrote: On Sunday 15 September 2002 20:08, Yenar Calentaure wrote: Hi Yenar, thanks for your kind and quick answer - I've got CVS write access, so does Chris. We'll be glad to take any patches and put them into CVS that would help automate the build process. I myself have a DSL line so up/download is not an issue for me; I could also use the 2mbit line in the company I work for now. Ben Burton and myself also have write access. Also, like Charles de Miramon pointed out, we should take care of daily or at least weekly builds from CVS that can be installed side by side of a stable environment for the translators and doc writers who need a recent KDE from CVS but can't/won't want to go through the development process. Do we have anyone willing to build them and host them? - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9haL+YsCKa6wDNXYRAuasAJ9jnxHJDeQVGlx+xYAS0GGVhisCvwCglbs7 /c6iwhEx+zL1ikAbv5U6ufQ= =ox/o -END PGP SIGNATURE-
Re: KDE debs building
måndagen den 16 september 2002 11.20 skrev David Pashley: I'm sorry that just isn't true. KDE HEAD has been kept up to date as much as possible. People have been able to build packages for 3.1 for the last few months. I could check the dates if you are interested. We haven't provided binary packages because a) they take up a lot of room and b) calc has been busy making sure that 3.0.x is working, bab has been working on koffice 1.2 and everyone else has been making sure that HEAD works. We have never said that we will start for on 3.1 debs once 3.1 has been released. Good you say it, since then I don't have to bother with building KDE 3.1 packages for others. Actually I never intended to and just made my own packages available, and was surprised by the demand. I am happy for the feedback I got on this list, and will improve my own packages and packaging technique. I have some plans and make small experiements on improvements, based on problems I have heard on this list, from all kind of KDE versions. If someone want my new packages for KDE 3.1 beta 2, when they come, I will make them available. But as you say, it is probably not needed since you already have done the work and hopefully will also provide binary packages. -- Karolina
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 12:09 pm, Karolina Lindqvist wrote: måndagen den 16 september 2002 11.20 skrev David Pashley: I'm sorry that just isn't true. KDE HEAD has been kept up to date as much as possible. People have been able to build packages for 3.1 for the last few months. I could check the dates if you are interested. We haven't provided binary packages because a) they take up a lot of room and b) calc has been busy making sure that 3.0.x is working, bab has been working on koffice 1.2 and everyone else has been making sure that HEAD works. We have never said that we will start for on 3.1 debs once 3.1 has been released. Good you say it, since then I don't have to bother with building KDE 3.1 packages for others. Actually I never intended to and just made my own packages available, and was surprised by the demand. I am happy for the feedback I got on this list, and will improve my own packages and packaging technique. I have some plans and make small experiements on improvements, based on problems I have heard on this list, from all kind of KDE versions. If you want to provide patches, we will gladly look at them. Just send them to the list. If someone want my new packages for KDE 3.1 beta 2, when they come, I will make them available. But as you say, it is probably not needed since you already have done the work and hopefully will also provide binary packages. I can't provide binaries, but I'm sure someone will. Hopefully it will start to get a bit less bumpy so when beta 2 is tagged, files won't be moved around so much. -- Karolina - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9hcYaYsCKa6wDNXYRAhX0AJ4rOZfRD5CxuM7bkKitH0jBPwMuzwCdGse1 CoPDUxjK75TDfUfVpLWOEgM= =Pw49 -END PGP SIGNATURE-
Re: KDE debs building
On Mon, Sep 16, 2002 at 01:33:27AM +0200, Ralf Nolden wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 15 September 2002 20:08, Yenar Calentaure wrote: Hi Yenar, thanks for your kind and quick answer - I've got CVS write access, so does Chris. We'll be glad to take any patches and put them into CVS that would help automate the build process. I myself have a DSL line so up/download is not an issue for me; I could also use the 2mbit line in the company I work for now. Ok. I have some time issues lately, but i'll try to contribute as much as possible. KDE on Debian is best system i had so far :). For now, i see one major problem with packaging of CVS. The list of installed files is somewhat in flux. For now, i had this idea: write perl script, that will parse control file containing regexp rules, run make -n install on sources, extract list of source and destination files and their attributes (executable, mode, etc.) and build file lists from these. Rules like: Package: kdelibs-bin Match-mode: executable Match-dest: /usr/bin/ Exclude-mode: others-write Package: kdelibs4 Match-dest: /usr/lib/kde3/.*so[0-9.-]*|/usr/lib/.*so[0-9.-]* Package: kdelibs-data Match-src: pics/| Match-dest: /usr/share (this is just to illustrate what i try to propose, not anything that matches reality) You know what i mean. I can make something like this this week (hopefully). I believe that most of package file-lists can be expressed this way more flexibly than with hardcoded filenames. And i believe that this can extend lifetime of packaging information, too. Sure, before release it should be hand-checked and fine-tuned, but i think it is good enough for cvs snapshots (if one or two files end up in wrong package, it won't end the world). Also, like Charles de Miramon pointed out, we should take care of daily or at least weekly builds from CVS that can be installed side by side of a stable environment for the translators and doc writers who need a recent KDE from CVS but can't/won't want to go through the development process. I'll try to convince my informatics teacher to let me upload my builds weekly :). I'll see what i can do. Btw., i build on woody. Ralf cheers yenar
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 September 2002 17:00, you wrote: Ralf Nolden wrote: On Monday 16 September 2002 15:08, peter rockai wrote: Fine, that would help. I've unstable here, so we would have two builds for debian, which is what everyone needs. My builds include having XFree 4.2.1 installed, if that is a requirement for the linking I guess, we should note that these packages only work with XFree 4.2.1. I would even go as far as mirroring the XFree 4.2.1 packages on ftp.kde.org :-) They will depend on them, I'd guess (dh_shlibdeps). Btw., is it possible to apt-get from ftp.kde.org? I build full apt-get repo (only missing release file atm). Then it would be as easy as adding ftp.kde.org into your sources list and apt-get update/install/upgrade. Don't know about the breakage when packages get renamed (as with arts last week :). That would be fine. We would need someone to set up the apt-get system on ftp.kde.org for us. Dirk, Daniel, how is the status with the ftp server ? Can we get access to that ? I messed a bit with Xft2 but i'll clean up my system to build correct woody debs. I'll improve automation of my build system, so it will work alone as far as possible. Most problems with cvs are from compile breakage :(. That's the part that I would like to do; keep up constantly compiling here, too. You can't avoid breakage one over the other day sometimes, especially on weekends; just that the debian dirs are updated ASAP after developers did changes (I build kde from cvs anyway so I would keep that up) Atm i don't build all the stuff (i don't have always time to fix problems in packages like kdepim or kdeaddons). But i can provide at least qt-copy, kdelibs, kdebase and koffice weekly. Kdemultimedia breaks because of old xine atm (so i'm forced to use ogg123 instead of noatun kdemultimedia works for me. I have noatun there :-) :). I'll have to build xine-lib-cvs package, too, as i see it :). I used the unstable packages. ftp.kde.org will end up as experimental addon for debian ;). Yes, that is the goal here. I cvsup every weekend, so i could upload on monday afternoon. I really hope that it will be possible. But i'll need to drop them somewhere, so if you could provide me with ftp address and login/pass, i would be glad. Yes, we'll do that; even if I would offer my box with an account for you and I would collect everything here and put the packages back on ftp if Daniel and Dirk won't be willing to give away too many password accounts. Builts should be done tuesdays/wednesdays after a cvsup because weekend updates tend to be having problems with compilation until monday afternoon/tuesday morning GMT Btw., is there someone on the server who could untar if i uploaded one huge tarball? I'll try to get automated upload of multiple files working at school, but i can't promise anything :(. Dunno. Maybe Dirk or Daniel know more about that. Ralf - -- We're not a company, we just produce better code at less costs. - Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9heWuu0nKi+w1Ky8RAiDfAJ9LC9wL4sJA+g9ODUt8n1T3XqWOFACfReI1 1ReHYE4gl9Vi6ZqgPvgSYRI= =TDGd -END PGP SIGNATURE-
Re: KDE debs building
Le Lundi 16 Septembre 2002 11:23, David Pashley a écrit : Also, like Charles de Miramon pointed out, we should take care of daily or at least weekly builds from CVS that can be installed side by side of a stable environment for the translators and doc writers who need a recent KDE from CVS but can't/won't want to go through the development process. Do we have anyone willing to build them and host them? It already exists (packaging quality should improve) http://matthieu.robin.free.fr/linux/
re: KDE debs building
On Mon, 16 Sep 2002, Yenar Calentaure wrote:
Another thing with debs I dislike atm: The package versions are the same all
the time. Sure, apt-get is smart enough to figure out what changed, but you
lose overview soon which build you run. I'll bump up version (probably best
scheme is 3.0.7-cvsMMDD) at each rebuild, and probably push the patch
upstream :). Likewise all changes to packaging should bump package version
(they should be mentioned in debian/changelog).
I'm using:
$ cat debian/rules
#!/usr/bin/make -f
#
# Based on Sample debian/rules file - for GNU Hello (1.3) by Ian Jackson.
#
# See realsync-files/debian/rules for details!
VERSION=${shell date +'%y%m%d%H%M%S'}
package=escher-cvs
[...]
binary-indep: build
[...usual stuff...]
dpkg-gencontrol -isp -v${VERSION} -DPackage=${package}-${VIDEO_DSCR}
dpkg --build debian/tmp ..
[...]
I suggest a note in README.Debian:
This package represents a daily build from CVS. Upstream changes are not
noted in the changelog
And I'd only mention stuff in the changelog if you really tighten some
Debian specific screw.
*t
--
---
Tomas Pospisek
SourcePole - Linux Open Source Solutions
http://sourcepole.ch
Elestastrasse 18, 7310 Bad Ragaz, Switzerland
Tel: +41 (81) 330 77 11
---
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 16 September 2002 18:08, Tomas Pospisek's Mailing Lists wrote:
Is the below rules file something we can reuse for that ? or are there other
options ? Then, why not importing it as rules.cvs into every module so we can
all reuse it for daily builds ?
Ralf
On Mon, 16 Sep 2002, Yenar Calentaure wrote:
Another thing with debs I dislike atm: The package versions are the same
all the time. Sure, apt-get is smart enough to figure out what changed,
but you lose overview soon which build you run. I'll bump up version
(probably best scheme is 3.0.7-cvsMMDD) at each rebuild, and probably
push the patch upstream :). Likewise all changes to packaging should bump
package version (they should be mentioned in debian/changelog).
I'm using:
$ cat debian/rules
#!/usr/bin/make -f
#
# Based on Sample debian/rules file - for GNU Hello (1.3) by Ian Jackson.
#
# See realsync-files/debian/rules for details!
VERSION=${shell date +'%y%m%d%H%M%S'}
package=escher-cvs
[...]
binary-indep: build
[...usual stuff...]
dpkg-gencontrol -isp -v${VERSION}
-DPackage=${package}-${VIDEO_DSCR} dpkg --build debian/tmp ..
[...]
I suggest a note in README.Debian:
This package represents a daily build from CVS. Upstream changes are not
noted in the changelog
And I'd only mention stuff in the changelog if you really tighten some
Debian specific screw.
*t
--
---
Tomas Pospisek
SourcePole - Linux Open Source Solutions
http://sourcepole.ch
Elestastrasse 18, 7310 Bad Ragaz, Switzerland
Tel: +41 (81) 330 77 11
---
- --
We're not a company, we just produce better code at less costs.
-
Ralf Nolden
[EMAIL PROTECTED]
The K Desktop Environment The KDevelop Project
http://www.kde.org http://www.kdevelop.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9hhkLu0nKi+w1Ky8RAtGMAKCd5Y9PE2IK7pnaEaLiAizILjUxAQCglmDM
J3nD2UWjVVsiqB0rpg8hiXg=
=L1ms
-END PGP SIGNATURE-
Re: KDE debs building
On Mon, 16 Sep 2002, Ralf Nolden wrote:
On Monday 16 September 2002 18:08, Tomas Pospisek's Mailing Lists wrote:
Is the below rules file something we can reuse for that ? or are there other
options ? Then, why not importing it as rules.cvs into every module so we can
all reuse it for daily builds ?
It's not the whole rules file mind you. It's only the relevant sections
that differ from the standard debmake (AFAI remember) rules file.
You will still have to adopt things since the debian tools will probably
not be able to automatically catch everything. But it might be a good
start.
On Mon, 16 Sep 2002, Yenar Calentaure wrote:
Another thing with debs I dislike atm: The package versions are the same
all the time. Sure, apt-get is smart enough to figure out what changed,
but you lose overview soon which build you run. I'll bump up version
(probably best scheme is 3.0.7-cvsMMDD) at each rebuild, and probably
push the patch upstream :). Likewise all changes to packaging should bump
package version (they should be mentioned in debian/changelog).
I'm using:
$ cat debian/rules
#!/usr/bin/make -f
#
# Based on Sample debian/rules file - for GNU Hello (1.3) by Ian Jackson.
#
# See realsync-files/debian/rules for details!
VERSION=${shell date +'%y%m%d%H%M%S'}
package=escher-cvs
[...]
binary-indep: build
[...usual stuff...]
dpkg-gencontrol -isp -v${VERSION}
-DPackage=${package}-${VIDEO_DSCR} dpkg --build debian/tmp ..
[...]
I suggest a note in README.Debian:
This package represents a daily build from CVS. Upstream changes are not
noted in the changelog
And I'd only mention stuff in the changelog if you really tighten some
Debian specific screw.
--
---
Tomas Pospisek
SourcePole - Linux Open Source Solutions
http://sourcepole.ch
Elestastrasse 18, 7310 Bad Ragaz, Switzerland
Tel: +41 (81) 330 77 11
---
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 16 September 2002 6:46 pm, Ralf Nolden wrote:
On Monday 16 September 2002 18:08, Tomas Pospisek's Mailing Lists wrote:
Is the below rules file something we can reuse for that ? or are there
other options ? Then, why not importing it as rules.cvs into every module
so we can all reuse it for daily builds ?
Ralf
There is a perl script (admin/debianrules) which generates the
debian/debiandirs makefile fragment.
On Mon, 16 Sep 2002, Yenar Calentaure wrote:
Another thing with debs I dislike atm: The package versions are the
same all the time. Sure, apt-get is smart enough to figure out what
changed, but you lose overview soon which build you run. I'll bump up
version (probably best scheme is 3.0.7-cvsMMDD) at each rebuild,
and probably push the patch upstream :). Likewise all changes to
packaging should bump package version (they should be mentioned in
debian/changelog).
I'm using:
$ cat debian/rules
#!/usr/bin/make -f
#
# Based on Sample debian/rules file - for GNU Hello (1.3) by Ian Jackson.
#
# See realsync-files/debian/rules for details!
VERSION=${shell date +'%y%m%d%H%M%S'}
package=escher-cvs
[...]
binary-indep: build
[...usual stuff...]
dpkg-gencontrol -isp -v${VERSION}
-DPackage=${package}-${VIDEO_DSCR} dpkg --build debian/tmp ..
[...]
I suggest a note in README.Debian:
This package represents a daily build from CVS. Upstream changes are not
noted in the changelog
And I'd only mention stuff in the changelog if you really tighten some
Debian specific screw.
*t
--
---
Tomas Pospisek
SourcePole - Linux Open Source Solutions
http://sourcepole.ch
Elestastrasse 18, 7310 Bad Ragaz, Switzerland
Tel: +41 (81) 330 77 11
---
--
We're not a company, we just produce better code at less costs.
Ralf Nolden
[EMAIL PROTECTED]
The K Desktop Environment The KDevelop Project
http://www.kde.org http://www.kdevelop.org
- --
David Pashley
[EMAIL PROTECTED]
Nihil curo de ista tua stulta superstitione.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9hjGWYsCKa6wDNXYRAkh4AJ9BITVs3ZJaD7Fg+7lEbmLIp0qiQQCgmdf5
909vxF8AS+qM8mPIzlofWZU=
=EmOb
-END PGP SIGNATURE-
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [ On Sunday 15 September 2002 10:35 am, Ralf Nolden wrote: ] [...] So it would be the best if we could somehow collect our resources and schedule building debs and providing them in a central place. [...] If you're interested, let's come together to finally end this messy system where there's certain problems with building debs for us and the KDE users using debian, it would surely make things a *lot* easier if we organize ourselves and coordinate doing things efficiently. Thanks for your attention and for volunteering :-) Ralf i try to avoid using bandwith on the list unless i have something of substance to contribute...but i can't help commenting on this. it would be simply wonderful. i recently tried suse, mandrake and redhat so i could use kde 3, but i didn't like them. i would quite pleased to have kde 3 on debian (i tried it but kmail messed up somewhere. i didn't catch it soon enough to know what happen). thanks, tim wheeler - -- Tim Wheeler [EMAIL PROTECTED] http://www.greengibberish.com/ - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9hLTGRNiK9b6/KqoRAslNAJ9F+SmRtSN/OZ/FL6Xf+ZtL1DFW8QCfY7/r fjKGg8x6jsDcnXjh/s6n8LQ= =MBjZ -END PGP SIGNATURE-
Re: KDE debs building
Ralf Nolden wrote: Hi, Hi [snip] /me has to agree. I talked with Dirk Müller already and some other guys that I use to work with at KDE and we should provide that possibility through KDE on ftp.kde.org. Wether that will work out just depends on how many people would volunteer to participate. I'd like to help. I build most of the debs on regular basis (each weekend) but unfortunately i'm seriously limited bandwidth-wise. I can provide patches to compile my favorite parts of kde on woody, though. Another thing is that qt-copy packaging in cvs is abandoned. I have working Qt 3.1 beta 1 mt packages, and i'll probably extend packaging to build non-mt versions, too. If someone could apply to cvs, i'd be glad :). If you're interested, let's come together to finally end this messy system where there's certain problems with building debs for us and the KDE users using debian, it would surely make things a *lot* easier if we organize ourselves and coordinate doing things efficiently. I'm definitely interested, but need someone to push my patches to cvs and to build debs for download. I can't work in kde cvs (i use cvsup due to internet connection issues) and have no write access anyway. If you are interested, i have mostly-working set of scripts to make building kde debs easier. This mostly consists of: ./build package something breaks, fix it ./build2 package (will continue where build stopped) ah, it completed this time (cd .. ./apt-archive) ./mkdiff package (will create patch from your changes) apt-get update apt-get upgrade (or apt-get install if you compile for first time) It needs quite a lot of space on harddrive and isn't particularly smart, but it works for me (tm). mkdiff doesn't work with qt-copy right now, but i'll fix that asap. Thanks for your attention and for volunteering :-) Thanks for nice initiative. Ralf - -- We're not a company, we just produce better code at less costs. - Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -- --- inetname: Yenar Calentaure realname: Peter Rockai mail: yenar(at)host.sk homepage: http://yenar.host.sk --- The universe is entering maintenance mode in 2 minutes. Please logout. -- Your administrator ---
Re: KDE debs building
Tim Wheeler [EMAIL PROTECTED] writes: i would quite pleased to have kde 3 on debian Garnome (http://www.gnome.org/~jdub/garnome/) has been able to build KDE3 for a while now, and it works just fine on Debian. It doesn't make packages or anything fancy like that, but it also doesn't touch things under /usr, so it's all good. john. -- In case you haven't heard, the Internet is not a superhighway. - Bill Washburn, _Internet_World_, Feb. 1995
Fwd: Re: KDE debs building
Hi Ralf, Sorting the 'mess'of KDE packages on Debian will be a very nice achievement. I would just like to point a specific problem for the KDE translators. When, like now, we are working on KDE 3.1, we need to have a CVS version of KDE to check the new applications and see in context the strings to be translated. Translators are generally not developpers, have slow computers, and not the skill to compile from CVS. For our use, Macolu (http://matthieu.robin.free.fr/linux/) has created some debs of KDE CVS version that can be installed side by side with a stable KDE in /opt/kde3cvs. You have to create a special user to use these debs and can use on the same box a stable and a experimental KDE. I think it would be nice and very useful to have a system like that that can create experimental snapshots debs of KDE (with names like kdebase-CVS, etc...) and generate stable debs when a new stable version comes out. By this way, Debian could become the reference distribution for the people (artists, translators, people writing documentation, bughunters, etc.) that need bleeding edge KDE but are unable or unwilling to compile from CVS. Cheers, Charles -- [EMAIL PROTECTED] http://www.kde-france.org
Re: KDE debs building
On Sunday 15 September 2002 4:35 pm, Ralf Nolden wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, as some of you got to know until now, I switched from SuSE to Debian this week - - and directly hit the fact that building debs from CVS would work best for me to have it working the right way (tm). Now, I got into working with Chris lately and we try to fix the issues one by one soon now so that everyone can build debs himself but more important, provide debs for KDE constantly that work, where also most importantly betas, RC's and finals are provided by the day that the packages are build and work optimal on Debian. Fantastic The other thing is that third party apps need to be compiled if you like to use them. Until now several people do that for the apps they like to run or that they are developing using debian as their development platform. The problem for the users is that the deb lines for sources.list are spread all over and there is no central way of getting the newest apps through debs for people that are not necessarily developers like we are. The other thing is that as developers, just doing a make install would work but that usually messes up our systems, especially as KDE has /usr as its prefix on debian. So it would be the best if we could somehow collect our resources and schedule building debs and providing them in a central place. Still not sure why KDE and these apps can't seem to make it into the formal debian unstable (and then the more stable) archive and mirrors, but apparently not - so ... I talked with Dirk Müller already and some other guys that I use to work with at KDE and we should provide that possibility through KDE on ftp.kde.org. Wether that will work out just depends on how many people would volunteer to participate. A good alternative - especially if you could set it up so that it had different sections for stable, unstable and development (or something) so that we could chose what. I am not sure how I could participate - I do have an always on, lightly used server supporting my family at home at the end of a cable modem, but my acceptable use conditions require that it is not used as a public server other than for a limited (10) password controlled connections. I could perhaps do some regular builds (Its only a p2 400 with 128MB Ram, but it has loads of disk space). As for my time, I am travelling abroad (from the UK) between 3 and 4 days a week, so that pretty much limits what I could do. I am trying to do some light coding or bug fixing offline in the evenings when I am away - but last weeks attempt was feeble, I managed only an hour (working late and then eating seems to grab most of the time). I could devote a bit more when I am at home. -- Alan Chandler [EMAIL PROTECTED]
Re: KDE debs building
I don't understand... Is kde3 not supposed to come into the official unstable/testing when the switch to gcc3.2 is done ? This should stop this mess. Why create another area ? Or will there be no/not enough people for maintaining kde when it comes into sid ?
Re: KDE debs building
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 15 September 2002 20:08, Yenar Calentaure wrote: Hi Yenar, thanks for your kind and quick answer - I've got CVS write access, so does Chris. We'll be glad to take any patches and put them into CVS that would help automate the build process. I myself have a DSL line so up/download is not an issue for me; I could also use the 2mbit line in the company I work for now. Also, like Charles de Miramon pointed out, we should take care of daily or at least weekly builds from CVS that can be installed side by side of a stable environment for the translators and doc writers who need a recent KDE from CVS but can't/won't want to go through the development process. Ralf Ralf Nolden wrote: Hi, Hi [snip] /me has to agree. I talked with Dirk Müller already and some other guys that I use to work with at KDE and we should provide that possibility through KDE on ftp.kde.org. Wether that will work out just depends on how many people would volunteer to participate. I'd like to help. I build most of the debs on regular basis (each weekend) but unfortunately i'm seriously limited bandwidth-wise. I can provide patches to compile my favorite parts of kde on woody, though. Another thing is that qt-copy packaging in cvs is abandoned. I have working Qt 3.1 beta 1 mt packages, and i'll probably extend packaging to build non-mt versions, too. If someone could apply to cvs, i'd be glad :). If you're interested, let's come together to finally end this messy system where there's certain problems with building debs for us and the KDE users using debian, it would surely make things a *lot* easier if we organize ourselves and coordinate doing things efficiently. I'm definitely interested, but need someone to push my patches to cvs and to build debs for download. I can't work in kde cvs (i use cvsup due to internet connection issues) and have no write access anyway. If you are interested, i have mostly-working set of scripts to make building kde debs easier. This mostly consists of: ./build package something breaks, fix it ./build2 package (will continue where build stopped) ah, it completed this time (cd .. ./apt-archive) ./mkdiff package (will create patch from your changes) apt-get update apt-get upgrade (or apt-get install if you compile for first time) It needs quite a lot of space on harddrive and isn't particularly smart, but it works for me (tm). mkdiff doesn't work with qt-copy right now, but i'll fix that asap. Thanks for your attention and for volunteering :-) Thanks for nice initiative. Ralf - -- We're not a company, we just produce better code at less costs. - Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org - -- We're not a company, we just produce better code at less costs. - Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9hRjOu0nKi+w1Ky8RAoX1AJ4wx/kFQMEgViG2+OUON8x7iuk0cwCbBDqB 6d9vplmd0E3srOlhwdl54Hw= =ImnE -END PGP SIGNATURE-
