Re: [ITP] Sendmail 8.14.9
Hi Yaakov, Yaakov Selkowitz wrote: On 2014-08-22 13:19, D. Boland wrote: On Aug 22 07:43, D. Boland wrote: I re-packaged Sendmail with cygport. See: http://cygwin.boland.nl/x86/release/sendmail/ Packaging looks good in theory. Unfortunately we have a problem. On inspection of your binary package I noticed that we have conflicts with exim and ssmtp packages: [snip] What we'll have to do to fix this problem is to convert all three packages to use alternatives. The alternatives package exists and is already used by a couple of other packages which would otherwise conflict, so there's precendent. And on Fedora, the various mail packages all use alternatives, too, to install their packages in parallel and conflict-free. [snip] You already guessed it. I don't like it. It's getting very messy this way. Not doing this properly will be even more messy, I assure you. I'm sorry for the following rant, [snip] Rants and flamewars really aren't helpful. The FOSS ecosystem not only allows for the possibility of alternative solutions, but thrives on it. So while we probably agree that sendmail is the first and in some ways a de-facto standard (at least in terms of program names and paths), and is certainly worthy of consideration for our distribution, it does not negate the legitimacy of exim/postfix/ssmtp/etc. Ok, that being out of the way: I am running out of time, and I still have to do the 64bit version. Running out of time for what? Keep in mind that being a package maintainer is more than just shipping a release and forgetting about it; given the nature of this package in particular, there are certainly going to be issues that come up from users. Dealing with this is part of the commitment of being a package maintainer. That being said, the more time we spend upfront doing this right should help mitigate even worse problems down the road should we not. Also, the 32-bit and 64-bit versions should be done together, particularly as we're going to have to rebuild other packages to make these all coexist. Therefore, it would be helpful if you could start working on the 64-bit ports in the meantime. Thanks for letting me have my rant. I put in my time and I will continue to do so. I think Sendmail, and for that matter, Redhat are worth it. You guys were the original believers in open source software, putting your own time and resources on the line. I still have an original 6.1 version running for 14 years now. Never crashed, never had problems. I've read the 'alternatives' documentation and it looks nasty: link groups, master link, slave link, automatic mode, manual mode... alternatives really isn't that hard to understand, and we'll help coordinate a working configuration for all the potentially conflicting MTAs. Why not let the user choose one program? Putting both Exim and Sendmail on one box is confusing, to say the least. Sendmail is very tough to understand. You don't want another (very similar looking) mail exchanger to add to the confusion. Cygwin's setup*.exe does not support the concept of conflicts (one package blocking others from being installed), nor does it prevent file clobbering if multiple packages provide the same file. Since there is no way to stop multiple MTAs from being installed, it is necessary to insure that they do so properly. Besides, at least in Fedora, it is possible to install multiple MTAs without conflicts. You really put me on the spot here. Will Sendmail suffer? Will it dream? This needs to be handled properly, that's all, and that can take time. If Pierre doesn't respond soon, we can step in to help with exim. So I will not be left alone with this. That's a relief. I'll wait with the uploading. In the mean time I'll update the Procmail and Sendmail code to use the new 'fakesu' lib. About the 64bit version: Are there any things I have to be careful of? Like crosscompiling? Or is it a matter of just straight forward compiling on a 64bit Cygwin machine? Daniel
[ITP] libfakesu 1.0
Hi Group, I intend to package this new Cygwin library. It was renamed due to name conflicts. See the following thread for more information: http://cygwin.com/ml/cygwin-apps/2014-08/msg00102.html It's waiting for upload at: http://cygwin.boland.nl/x86/release/libfakesu/ Daniel
Re: [ITP] libfakesu 1.0
D. Boland writes:
It's waiting for upload at:
http://cygwin.boland.nl/x86/release/libfakesu/
cygmake install PREFIX=${D}/usr
You wouldn't need to do this if your Makefile was using $(DESTDIR) for
supporting staged builds. Otherwise, packaging looks OK to me -- GTG.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: Deafult to bash so $chere will work (possibly?)
Greetings, Michelle Pace! I would like Cygwin in the context menu of my Windows 7 machine (I have admin rights). I'm not sure really why the chere command is not working It works as long as you get the context menu entry after it's invocation. since I've just read sh is actually really bash That's right, it IS bash in Cygwin, but... and my .bashrc file is definitely getting used. Additionally there is nothing in my passwd file as I thought I should just replace sh with bash. Finally, setting $SHELL to /bin/bash also did not work. The devil is in the details. When you don't explicitly call bash, it is getting called as /bin/sh and fall back to POSIX compatibility mode. QUESTION: Could anyone please point out what I need to do to get my chere command working? Simple answer: you're doing it wrong. But that's not enough - you're not reading/ignoring what the tool tell you. --- My Story --- $ chere -i -t mintty Shell defaulting to sh defined for MP /usr/bin/chere Error: Unknown shell sh chere -t mintty -s bash or -s /bin/bash, I dunno... -- WBR, Andrey Repin (anrdae...@yandex.ru) 24.08.2014, 11:32 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: top and free fail as of 21 Aug
On Aug 23 08:11, Lester Ingber wrote: As of 21 Aug 2014, under cygwin, top and free return a blank line. I uploaded the 64 bit tar file for 32 bit as well, accidentally. I fixed that now by uploading a 32 bit 3.2.8-4. HTH, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpydGlCFLfbj.pgp Description: PGP signature
Re: Deafult to bash so $chere will work (possibly?)
HOORAY! Thanks Andrey, this command worked for me: $ chere -i -t mintty -s bash DAYS of trying to figure this out. Thank-you! Michelle PS No problems about the english - it's better than my Russian :) On 24 August 2014 09:36, Andrey Repin anrdae...@yandex.ru wrote: Greetings, Michelle Pace! I would like Cygwin in the context menu of my Windows 7 machine (I have admin rights). I'm not sure really why the chere command is not working It works as long as you get the context menu entry after it's invocation. since I've just read sh is actually really bash That's right, it IS bash in Cygwin, but... and my .bashrc file is definitely getting used. Additionally there is nothing in my passwd file as I thought I should just replace sh with bash. Finally, setting $SHELL to /bin/bash also did not work. The devil is in the details. When you don't explicitly call bash, it is getting called as /bin/sh and fall back to POSIX compatibility mode. QUESTION: Could anyone please point out what I need to do to get my chere command working? Simple answer: you're doing it wrong. But that's not enough - you're not reading/ignoring what the tool tell you. --- My Story --- $ chere -i -t mintty Shell defaulting to sh defined for MP /usr/bin/chere Error: Unknown shell sh chere -t mintty -s bash or -s /bin/bash, I dunno... -- WBR, Andrey Repin (anrdae...@yandex.ru) 24.08.2014, 11:32 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Deafult to bash so $chere will work (possibly?)
On 24/08/2014 11:02, Michelle Pace wrote: HOORAY! Thanks Andrey, this command worked for me: $ chere -i -t mintty -s bash I'm glad you got it to work. chere is attempting to use the shell defined in your passwd (as retrieved by getent). The shell being returned is '/bin/sh'. It looks like I forget to add an entry handle to handle sh... I'll try to fix this up for the next version. Thanks for the report, Dave. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Prompt at bottom of terminal
Hi there, This would seem a somewhat arbitrary question but it is driving me crazy. The prompt on my terminal starts from the bottom of the terminal. Could anyone tell me how I get it to start from the top left hand corner like normal? The Target of the icon which I use to start cygwin with is: C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico - Thanks in advance, Michelle -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
