komport-devel Mailing List for Komport (Page 2)
Status: Alpha
Brought to you by:
msharkey
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(17) |
Dec
(31) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Mike S. <mi...@sh...> - 2003-12-03 19:21:28
|
Oh yes, I forgot to mention the updates which where part of the subject line in my previous post. I just committed a few updates to the repository which include, enable visual bell function (please let me know how you feel about how it looks), and also some minor revisions to the settings form. On Monday 01 December 2003 04:36 am, Mike Sharkey wrote: > I'm just thinking about initiating the connection. > > As it is now, Komport will initiate a connection on startup, after first > reading the config (komportrc) file. I don't think this is that good in > all cases. For example, take the case that you just installed Komport and > it immediately wants to open /dev/ttyS0 (which is the default port) and you > happen to allready have a serial mouse connected to /dev/ttyS0. This is not > that good because there is now a conflict. > > So, what I am thinking about is how to make a user interface for > initiating a connection. Personally, I like the current behavior of > initiating a connection on startup simply because I don't have to do > anything to initiate the connection, and I can just go ahead and start > typing. However, I can see that there might be circumstances that may > require komport to hold off on connecting until such a connection command > is given. > > So, I am thinking about a settings form checkbox like "connect on startup". > And also a menu/toolbar component for connecting and disconnecting. > > Also there is the issue of "per connection" settings files. Now, the > thought behind this being that if I connect to different devices, (or > different BBS sites, or whatever), I want to be able to save the device > settings separately and be able to access them in a convenient way. > > So my question is further complicated by the question wether or not the > "connect on startup" function should apply globally, or to individual > connection settings. > > Anyway, I'll think about this over a few Red Cap Ales, meanwhile I'd > appreciate any thoughts. > > Cheers! > > --Mike > > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Komport-devel mailing list > Kom...@li... > https://lists.sourceforge.net/lists/listinfo/komport-devel |
From: Mike S. <mi...@sh...> - 2003-12-03 18:43:03
|
I'm just thinking about initiating the connection. As it is now, Komport will initiate a connection on startup, after first reading the config (komportrc) file. I don't think this is that good in all cases. For example, take the case that you just installed Komport and it immediately wants to open /dev/ttyS0 (which is the default port) and you happen to allready have a serial mouse connected to /dev/ttyS0. This is not that good because there is now a conflict. So, what I am thinking about is how to make a user interface for initiating a connection. Personally, I like the current behavior of initiating a connection on startup simply because I don't have to do anything to initiate the connection, and I can just go ahead and start typing. However, I can see that there might be circumstances that may require komport to hold off on connecting until such a connection command is given. So, I am thinking about a settings form checkbox like "connect on startup". And also a menu/toolbar component for connecting and disconnecting. Also there is the issue of "per connection" settings files. Now, the thought behind this being that if I connect to different devices, (or different BBS sites, or whatever), I want to be able to save the device settings separately and be able to access them in a convenient way. So my question is further complicated by the question wether or not the "connect on startup" function should apply globally, or to individual connection settings. Anyway, I'll think about this over a few Red Cap Ales, meanwhile I'd appreciate any thoughts. Cheers! --Mike |
From: Mike S. <mi...@sh...> - 2003-12-03 16:25:58
|
I have not had any experience with the actual KDE localization process either. What I do know is that for it to work, all of the application text strings (in english or whatever the original language) have to get passed through a function called i18n(). I also know that there are language resource files (.po files) which are somehow edited using a program called KBabel (there are also other such editors). Somehow, any strings which get passed through the i18n() function will then magically get translated using the appropriate .po resource file depending on KDE language settings. Assuming there is an appropriate translated string found, then it is used, otherwise the original language string is passed through by default. Presumably there is some kind of hash code generated from the original language string which is used as a key to index into the alternate language resource file. In any case, thank you for the kind offer. Robert has already volunteered to do a German translation. He sounds as if he has had experience with this, but it is always good to know we have someone on standby for backup. :) English is my only language (my wife is Lithuanian so I am capable of some very poor Lithuanian only) but I know people locally that can translate to French, Lithuanian, Italian, Russian, and Polish. I will be getting those people to translate the strings on paper, then I will generate the .po files, so it will be a good experience to go through the whole process myself so I'll know better what I'm talking about. On Wednesday 03 December 2003 10:22 am, Steven Kreuzer wrote: > I'm not quite sure how localization works and if it is done automatically, > but if you need someone to help translate to German, let me know. |
From: Steven K. <skr...@f2...> - 2003-12-03 15:22:48
|
I'm not quite sure how localization works and if it is done automatically, but if you need someone to help translate to German, let me know. > I was able to make a few changes this morning and committed them to the > repository. > > I've added a file called komportstrings.h which contains all of the > application i18n text strings for localization. The strings I've done so > far > are the menus, tootips, and status text. I have not yet done the settings > dialog as I need to revise the settings form first. > > Also I've fixed some scrolling issues, vertical scroll bar now scrolls by > line > rather than by pixel, and pages by one screen. Also history limit is now > working properly again. > > Printing the screen was broken in 0.5.8 and is now fixed since 0.5.9. > > I did a little optimization in the KomportCell cell class, both for memory > consumption and performance. > > Please everyone have a look at the latest TODO file (for 0.6) and let > everyone > know if you have anything to add, subtract, modify, or discuss. > > Enjoy! > > --Mike > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Komport-devel mailing list > Kom...@li... > https://lists.sourceforge.net/lists/listinfo/komport-devel > |
From: Mike S. <mi...@sh...> - 2003-12-03 14:46:04
|
Is there anyone on the list who is artistically inclined by any chance? Perhaps if you are, you might come up with a graphic to use as an application icon. When it comes to artistic creativity, let's just say, it's best that I don't do it. Should I maybe post a "help wanted" ad on sf? --Mike |
From: Mike S. <mi...@sh...> - 2003-12-03 14:00:04
|
I was able to make a few changes this morning and committed them to the repository. I've added a file called komportstrings.h which contains all of the application i18n text strings for localization. The strings I've done so far are the menus, tootips, and status text. I have not yet done the settings dialog as I need to revise the settings form first. Also I've fixed some scrolling issues, vertical scroll bar now scrolls by line rather than by pixel, and pages by one screen. Also history limit is now working properly again. Printing the screen was broken in 0.5.8 and is now fixed since 0.5.9. I did a little optimization in the KomportCell cell class, both for memory consumption and performance. Please everyone have a look at the latest TODO file (for 0.6) and let everyone know if you have anything to add, subtract, modify, or discuss. Enjoy! --Mike |
From: Mike S. <mi...@sh...> - 2003-12-03 01:19:58
|
Hi All, I think I've successfully committed the changes to bring the repository up to the latest 0.5.9 version (I had to make a few bug fixes after 0.5.8). People should now be able to build the latest from the repository. Let me know how it goes, please. Everyone involved in the project should have write access to the repository. Please let me know if you need an adjustment to your privileges. Mark, I'm hoping you will keep everyone in line with respect to repository discipline. Maybe you could draft a set of basic guidelines. What I would like is to be able to have tags or some mechanism to get to the last buildable and runnable version. Anyone else have any input on repository discipline? Should we have a "stable" and "unstable" branch perhaps? I don't know, I'm asking the CVS experts. In any case, I will be working from CVS from now on. Any of you who are interested in doing some KDE/C++ programming, please by all means feel free. :) A few house keeping chores and some TODO items I think we should get done over the next little while: * Put all string constants into one header file to simplify localization as per Robert's earlier suggestion. * Update the ChangeLog, AUTHORS, README, TODO files to contain useful information..... * Get package files (.spec, etc...) into repository. I'll work on the TODO list next, as I think that's my biggest task right now is to prioritize coding items for the 0.6 release. Well, it's really looking good, thanks everyone for helping out! Cheers all! --Mike |
From: Mike S. <mi...@sh...> - 2003-12-02 19:45:14
|
Sorry, I meant that I tagged 0.5.3 *not* 0.5.8 --Mike On Sunday 30 November 2003 05:31 am, Mike Sharkey wrote: > I tagged 0.5.8 (I later saw Mark had already tagged > it - sorry Mark - I'll leave such things to you in the future). |
From: Mike S. <mi...@sh...> - 2003-12-02 19:37:57
|
Hi all, I would like everyone (including myself) to be begin to be able to work directly from CVS. I'm just wondering how would be the best way to get the latest source (0.5.8pre0.6) into CVS. I tagged 0.5.8 (I later saw Mark had already tagged it - sorry Mark - I'll leave such things to you in the future). Should I just merge my changes locally then commit them, or perhaps we should do a branch or what? Anyway, consider 0.5.8 to be the latest source and I will make no further changes until after we get the latest changes into CVS. --Mike |
From: Mike S. <mi...@sh...> - 2003-12-02 17:45:27
|
Hi guys, Here's komport 0.5.8 pre-0.6: ftp://sharkey.servebeer.com/pub/komport/komport-0.5.8.tar.gz Please get it and try doing a build. KomportView is almost completely rewritten so I want to see if there are any major problems before we release 0.6. Please reply to the list with any trouble building or any strangeness that you think should be addressed before 0.6 You should see much smoother scrolling, and much smoother text selection. Also, overall there should be an improvement in screen drawing speed. There is still a bit of an issue with the scroll bars encroaching on the viewport area that I already know about and I will address that before 0.6 --Mike |
From: Mike S. <mi...@sh...> - 2003-12-02 12:31:25
|
Cool! I'll be checking out later today and I'll report back how it goes. --Mike On Tuesday 02 December 2003 02:56 am, Mark wrote: > As of earlier today, Komport is in the SourceForge CVS repository. For the > source code checkout the module 'src' as previous mentioned. It has the > source of the last release and ready for any changes. > > The modules for distribution are next on my list which hopefully will take > almost no time. > > ______________________________________________________________________ > Post your free ad now! http://personals.yahoo.ca > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Komport-devel mailing list > Kom...@li... > https://lists.sourceforge.net/lists/listinfo/komport-devel |
From: Mark <mb...@ya...> - 2003-12-02 07:56:02
|
As of earlier today, Komport is in the SourceForge CVS repository. For the source code checkout the module 'src' as previous mentioned. It has the source of the last release and ready for any changes. The modules for distribution are next on my list which hopefully will take almost no time. ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca |
From: Steven K. <skr...@f2...> - 2003-11-26 02:17:25
|
Hey Mike, I noticed that you posted the SRPM for download, but didn't post the RPM. Is there any reason for that? SK |
From: Mike S. <mi...@sh...> - 2003-11-25 19:55:56
|
Just to clarify, my intention is to include people's @user.sourceforge.net email address unless otherwise specified. --Mike On Sunday 23 November 2003 05:31 am, Mike Sharkey wrote: > Starting in the 0.6 code stream, I would like to include an > "About->Credits" form to acknowledge people that have been helping out. > Anyone who does NOT want their name and/or email address included, please > email me off-list. > > Thanks > > --Mike > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Komport-devel mailing list > Kom...@li... > https://lists.sourceforge.net/lists/listinfo/komport-devel |
From: Mike S. <mi...@sh...> - 2003-11-25 19:37:43
|
Starting in the 0.6 code stream, I would like to include an "About->Credits" form to acknowledge people that have been helping out. Anyone who does NOT want their name and/or email address included, please email me off-list. Thanks --Mike |
From: Mark <mb...@ya...> - 2003-11-24 03:01:44
|
To give you an idea of what's going on from my end, I have had trouble accessing SourceForge's CVS. Probably something at my end regarding the usage of SSH and have raised the issue with SF. Once I get going, I see no problem using a SSH key to access CVS, this initial issue is kind of strange so I will see what SF Support says. (I've already gotten to they're 2nd level of support.) Should be soon! Regarding other issues raised on the mailing list, I like the idea of setting up the 'dist' folder with various formats and as soon as I get access ... With having the web site in CVS, I think there are ways to work with it all. I have no problem helping out or updating the web site every so often as a backup that's stored in CVS. We can talk more when I finally get CVS going. Should have some kind of update on Monday. ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca |
From: Mike S. <mi...@sh...> - 2003-11-22 18:18:56
|
I'm working a good part of this weekend on getting a Debian box upgraded and back online. It's a Motorola 68k architecture but probably I will encounter the same problems. In any case, I'll make whatever changes are nessesary to compile it on Debian and I'll report my results on this list. --Mike I'll report On Saturday 22 November 2003 08:09 am, Wim Stubbe wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I' like komport, and if possible would create debian packages. But I seem > to have problems compiling on Debian. Anyone have any ideas how to solve > it? > > Here's what I get: > > make all-recursive > make[1]: Entering directory `/home/wim/ttt/komport-0.5.3' > Making all in komport > make[2]: Entering directory `/home/wim/ttt/komport-0.5.3/komport' > rm -f settingsdialog.cpp > echo '#include <klocale.h>' > settingsdialog.cpp > /usr/bin/uic -L /usr/local/kde/lib/kde3/plugins/designer -nounload -tr > tr2i18n - -i settingsdialog.h ./settingsdialog.ui | sed -e > "s,tr2i18n( \"\" ),QString::null,g" | sed -e "s,tr2i18n( \"\"\, > \"\" ),QString::null,g" | sed -e "s,image\([0-9][0-9]*\)_data,img > \1_settingsdialog,g" >> settingsdialog.cpp || rm -f settingsdialog.cpp > echo '#include "settingsdialog.moc"' >> settingsdialog.cpp > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/kde -I/usr/include/qt3/ -I/ > usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -fno-exceptions > - -fno-check-new -c settingsdialog.cpp > settingsdialog.cpp: In constructor > `SettingsDialog::SettingsDialog(QWidget*, const char*, bool, unsigned > int)': > settingsdialog.cpp:137: error: invalid use of undefined type `struct > KURLRequester' > settingsdialog.h:19: error: forward declaration of `struct KURLRequester' > settingsdialog.cpp:138: error: `setEnabled' undeclared (first use this > function) > settingsdialog.cpp:138: error: (Each undeclared identifier is reported only > once for each function it appears in.) > settingsdialog.cpp:139: error: `setGeometry' undeclared (first use this > function) > settingsdialog.cpp:220: error: no matching function for call to > `SettingsDialog > > ::connect(QRadioButton*&, const char[15], KURLRequester*&, const > :: char[18])' > > /usr/include/qt3/qobject.h:116: error: candidates are: static bool > QObject::connect(const QObject*, const char*, const QObject*, const > char*) /usr/include/qt3/qobject.h:227: error: bool > QObject::connect(const QObject*, const char*, const char*) const > make[2]: *** [settingsdialog.o] Error 1 > make[2]: Leaving directory `/home/wim/ttt/komport-0.5.3/komport' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/wim/ttt/komport-0.5.3' > make: *** [all-recursive-am] Error 2 > bash-2.05b$ > > - -- > http://www.openstandaarden.be > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.3 (GNU/Linux) > > iD8DBQE/v2Ab/KNYPBSQUjsRAsuUAKCvhGCRWH1TBX7nIBr004OGQb8utQCeKR7c > ocpbXjmi1b4+8tRWpyXsOCo= > =cf3G > -----END PGP SIGNATURE----- > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Komport-devel mailing list > Kom...@li... > https://lists.sourceforge.net/lists/listinfo/komport-devel |
From: Wim S. <wi...@li...> - 2003-11-22 13:11:36
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,=20 I' like komport, and if possible would create debian packages. But I seem t= o=20 have problems compiling on Debian. Anyone have any ideas how to solve it? Here's what I get: make all-recursive make[1]: Entering directory `/home/wim/ttt/komport-0.5.3' Making all in komport make[2]: Entering directory `/home/wim/ttt/komport-0.5.3/komport' rm -f settingsdialog.cpp echo '#include <klocale.h>' > settingsdialog.cpp /usr/bin/uic -L /usr/local/kde/lib/kde3/plugins/designer -nounload -tr tr2i= 18n=20 =2D -i settingsdialog.h ./settingsdialog.ui | sed -e=20 "s,tr2i18n( \"\" ),QString::null,g" | sed -e "s,tr2i18n( \"\"\,=20 \"\" ),QString::null,g" | sed -e "s,image\([0-9][0-9]*\)_data,img \1_settingsdialog,g" >> settingsdialog.cpp || rm -f settingsdialog.cpp echo '#include "settingsdialog.moc"' >> settingsdialog.cpp c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/kde -I/usr/include/qt3/ -I/ usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -fno-exceptions= =20 =2D -fno-check-new -c settingsdialog.cpp settingsdialog.cpp: In constructor `SettingsDialog::SettingsDialog(QWidget*, const char*, bool, unsigned int)': settingsdialog.cpp:137: error: invalid use of undefined type `struct KURLRequester' settingsdialog.h:19: error: forward declaration of `struct KURLRequester' settingsdialog.cpp:138: error: `setEnabled' undeclared (first use this function) settingsdialog.cpp:138: error: (Each undeclared identifier is reported only once for each function it appears in.) settingsdialog.cpp:139: error: `setGeometry' undeclared (first use this function) settingsdialog.cpp:220: error: no matching function for call to=20 `SettingsDialog ::connect(QRadioButton*&, const char[15], KURLRequester*&, const char[18= ])' /usr/include/qt3/qobject.h:116: error: candidates are: static bool QObject::connect(const QObject*, const char*, const QObject*, const char= *) /usr/include/qt3/qobject.h:227: error: bool QObject::connect(const QObject*, const char*, const char*) const make[2]: *** [settingsdialog.o] Error 1 make[2]: Leaving directory `/home/wim/ttt/komport-0.5.3/komport' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/wim/ttt/komport-0.5.3' make: *** [all-recursive-am] Error 2 bash-2.05b$ =2D --=20 http://www.openstandaarden.be =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/v2Ab/KNYPBSQUjsRAsuUAKCvhGCRWH1TBX7nIBr004OGQb8utQCeKR7c ocpbXjmi1b4+8tRWpyXsOCo=3D =3Dcf3G =2D----END PGP SIGNATURE----- |
From: <skr...@f2...> - 2003-11-21 21:46:41
|
CVS is rather easy to learn, and there is a nice front end (if your using windows) called TortoiseCVS <http://www.tortoisecvs.org> so you don't have to mess around with the command line. I would suggest you give it a try, it might make your life easier in the long run. SK > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Mark wrote: > | [...] To make it logical, I figured the > | following > | would work best (somewhat from experience): > | > | src - the source to komport > | www - the web site on SF > > Is it necessary to have the website data in cvs? > > This is a little bit troublesome for me because I do not have practical > experience in using cvs. > > As far as I think the source code will change more often than the website. > > Best regards, > ~ Robert Bachmann > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (MingW32) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQE/voHlrtl+VJAX6poRAsPrAJ0RFQFTYkklF68Bt2nEfHmT1AYS0gCfYx86 > TyyXjLqb4tqKhsRU9l8EBoc= > =rn1n > -----END PGP SIGNATURE----- > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Komport-devel mailing list > Kom...@li... > https://lists.sourceforge.net/lists/listinfo/komport-devel > |
From: Mike S. <mi...@sh...> - 2003-11-21 21:45:08
|
Robert, In my opinion, your reasoning is correct. I feel it's fine if you don't use CVS for the website. Also, while on the subject of the website, I think the old website files can be taken offline the next time you work on the website unless anyone can point out a good reason to keep them around. Also, I've made some significant code changes today, rewriting most of KomportView so that KomportView class is derived directly from QScrollView for various reasons which I think will be benificial moving forward. What this means is, I have some 0.5 stream changes that make some improvements that should probably go into CVS and that should be a pretty stable version for the time being. Then we're starting a new 0.6 stream with the new KomportView class, which, after major surgery is pretty much unstable. So, Mark, perhaps I should send you a tar ball of the most recent 0.5 code so you can put that into CVS as a stable stream, then as soon as I get a clean compile and run from 0.6 I can give you that and it will be unstable. Maybe we can just tag them or something "stable", and "unstable" if that makes sense to do? --Mike On Friday 21 November 2003 04:21 pm, Robert Bachmann wrote: > Is it necessary to have the website data in cvs? > > This is a little bit troublesome for me because I do not have practical > experience in using cvs. > > As far as I think the source code will change more often than the website. > > Best regards, > ~ Robert Bachmann > |
From: Robert B. <Rob...@rb...> - 2003-11-21 21:19:36
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark wrote: | [...] To make it logical, I figured the | following | would work best (somewhat from experience): | | src - the source to komport | www - the web site on SF Is it necessary to have the website data in cvs? This is a little bit troublesome for me because I do not have practical experience in using cvs. As far as I think the source code will change more often than the website. Best regards, ~ Robert Bachmann -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQE/voHlrtl+VJAX6poRAsPrAJ0RFQFTYkklF68Bt2nEfHmT1AYS0gCfYx86 TyyXjLqb4tqKhsRU9l8EBoc= =rn1n -----END PGP SIGNATURE----- |
From: <skr...@f2...> - 2003-11-21 17:30:19
|
Mark, you said that you are going to create a module called dist that will be where all the packaging stuff goes. Do me a favor and create a folder structure that looks like this: dist/ |___ deb/ |___ rpm/ |___ BUILD/ |___ RPMS/ |___ SOURCES/ |___ SPEC/ |___ SRPMS/ This will pretty much setup the environment I need to build RPM packages and will allow us to also create a "workbench" for making other packages (such as .deb or whatnot) in the future. Also, if you need some help with the CVS stuff, I have some experiance with setting up CVS servers at work for inhouse projects. Contact me off list and I'll give you my cell number SK > I'm in the process of working on the alternative that SF uses. It > involves > posting a SSH key to access the CVS repository but I'm just checking out > how > well it works. (I am not familiar with KDevelop so I will check to see > what > functionality it has and see what the possibilities are... ) > > I'm thinking about putting everything in CVS on Saturday. I have a couple > issues to resolve with SF at this moment which should be cleared up soon. > Of > course if we have issues we can follow through with your suggestion. > > On Wednesday 19 November 2003 09:02 pm, Mark wrote: >> > As Mike mentioned, I am going to set up the CVS repository. I've >> started >> > the prep on SourceForge and wanted to get some impressions prior to my >> > committing any information. I've done some review of their documents >> and >> > will try and get the most of what they allow. Particularly dealing >> with >> > the issue about CVS through SSH which requiring constant password >> prompts >> > (from my understanding at least.) >> >> Yeah, I read a little about that ssh deal on sourceforge and it did not >> sound >> that cool to me from a convenience standpoint as I would like to use >> the CVS >> functions in KDevelop it does not sound to me that they will work with >> that >> setup, but I didn't go into it in great detail so perhaps I missed >> something. >> >> I think to get things started, maybe we should just try getting >> everything in >> CVS on sourceforge, then I'll merge in my recent changes, and then maybe >> we >> can try doing a complete build from sourceforge CVS and just see how the >> whole process goes and what problems we run into. Then I think we should >> make >> a decision if it's working for us or not. >> >> If we decide at that point that it's not working well enough for day to >> day >> CVS use, then there is the option of setting up a CVS server on >> sharkey.servebeer.com for our daily use (maybe using the firewall to >> limit >> access to our IP address ranges only), then once in a while mirror it >> onto >> sourceforge, probably a daily cron script could do that. >> >> Does that sound like a reasonable approach? > > ______________________________________________________________________ > Post your free ad now! http://personals.yahoo.ca > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Komport-devel mailing list > Kom...@li... > https://lists.sourceforge.net/lists/listinfo/komport-devel > |
From: Mark <mb...@ya...> - 2003-11-21 04:57:27
|
I'm in the process of working on the alternative that SF uses. It involves posting a SSH key to access the CVS repository but I'm just checking out how well it works. (I am not familiar with KDevelop so I will check to see what functionality it has and see what the possibilities are... ) I'm thinking about putting everything in CVS on Saturday. I have a couple issues to resolve with SF at this moment which should be cleared up soon. Of course if we have issues we can follow through with your suggestion. On Wednesday 19 November 2003 09:02 pm, Mark wrote: > > As Mike mentioned, I am going to set up the CVS repository. I've started > > the prep on SourceForge and wanted to get some impressions prior to my > > committing any information. I've done some review of their documents and > > will try and get the most of what they allow. Particularly dealing with > > the issue about CVS through SSH which requiring constant password prompts > > (from my understanding at least.) > > Yeah, I read a little about that ssh deal on sourceforge and it did not sound > that cool to me from a convenience standpoint as I would like to use the CVS > functions in KDevelop it does not sound to me that they will work with that > setup, but I didn't go into it in great detail so perhaps I missed something. > > I think to get things started, maybe we should just try getting everything in > CVS on sourceforge, then I'll merge in my recent changes, and then maybe we > can try doing a complete build from sourceforge CVS and just see how the > whole process goes and what problems we run into. Then I think we should make > a decision if it's working for us or not. > > If we decide at that point that it's not working well enough for day to day > CVS use, then there is the option of setting up a CVS server on > sharkey.servebeer.com for our daily use (maybe using the firewall to limit > access to our IP address ranges only), then once in a while mirror it onto > sourceforge, probably a daily cron script could do that. > > Does that sound like a reasonable approach? ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca |
From: Mike S. <mi...@sh...> - 2003-11-20 14:47:39
|
On Wednesday 19 November 2003 09:02 pm, Mark wrote: > As Mike mentioned, I am going to set up the CVS repository. I've started > the prep on SourceForge and wanted to get some impressions prior to my > committing any information. I've done some review of their documents and > will try and get the most of what they allow. Particularly dealing with > the issue about CVS through SSH which requiring constant password prompts > (from my understanding at least.) Yeah, I read a little about that ssh deal on sourceforge and it did not sound that cool to me from a convenience standpoint as I would like to use the CVS functions in KDevelop it does not sound to me that they will work with that setup, but I didn't go into it in great detail so perhaps I missed something. I think to get things started, maybe we should just try getting everything in CVS on sourceforge, then I'll merge in my recent changes, and then maybe we can try doing a complete build from sourceforge CVS and just see how the whole process goes and what problems we run into. Then I think we should make a decision if it's working for us or not. If we decide at that point that it's not working well enough for day to day CVS use, then there is the option of setting up a CVS server on sharkey.servebeer.com for our daily use (maybe using the firewall to limit access to our IP address ranges only), then once in a while mirror it onto sourceforge, probably a daily cron script could do that. Does that sound like a reasonable approach? > > To try and keep things separated, I figured the best structure was 3 > modules so everyone has a separate module. To make it logical, I figured > the following would work best (somewhat from experience): > > src - the source to komport > www - the web site on SF > dist - this would be for the packaging of what is released > > To keep things easy, I'll keep the src directory as the tar which was > provided as the initial release. (In the future, I'll see if SF allows > some tasks where I can tar the source and put a copy in the dist directory. > Assuming it works for everyone.) I think that should be okay. > > Any suggestions or thoughts are welcome. > > Mark --Mike |
From: Mark <mb...@ya...> - 2003-11-20 02:03:39
|
Hi everyone, As Mike mentioned, I am going to set up the CVS repository. I've started the prep on SourceForge and wanted to get some impressions prior to my committing any information. I've done some review of their documents and will try and get the most of what they allow. Particularly dealing with the issue about CVS through SSH which requiring constant password prompts (from my understanding at least.) To try and keep things separated, I figured the best structure was 3 modules so everyone has a separate module. To make it logical, I figured the following would work best (somewhat from experience): src - the source to komport www - the web site on SF dist - this would be for the packaging of what is released To keep things easy, I'll keep the src directory as the tar which was provided as the initial release. (In the future, I'll see if SF allows some tasks where I can tar the source and put a copy in the dist directory. Assuming it works for everyone.) Any suggestions or thoughts are welcome. Mark ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca |