Re: [Cooker] msec flaw
On 11 May 2002 12:21:13 +0400 Borsenkow Andrej <[EMAIL PROTECTED]> wrote:
> ÷ óÂÔ, 11.05.2002, × 04:41, Todd Lyons ÎÁÐÉÓÁÌ:
> > Pierre Fortin wrote on Thu, May 09, 2002 at 04:30:12PM -0400 :
> > > >
> > > > 711 on /home/* is enough for, for example apache..
> > > My preference is to not make *any* directory more open by any automated
> > > process. If I choose 700 for /home/root, I consider it a security issue
> > > for something like msec to make it less secure behind my back.
> >
> > You're suggesting that a default policy be to never loosen permissions
> > on a {target}, but if the current security level wants it tighter, go
> > ahead and do it.
> >
>
> That makes sense. But ...
>
> file have permissions: 760
> msec wants it to be: 704
>
> What should be applied (silly example, I know)? Or do you mean "for
> user, group and others separately"?
>
> I guess what is needed is to tell msec to preserve permissions. Then let
> user say
>
>
> /home/* preserve
> /home/xxx 711
>
> if he needs it.
>
> -andrej
>
>
I'd go with doing each part individually, without user having to do anything.
--
Grimau Lysik'an, the Bionic Elf
---
Mandrake on irc.openprojects.net:
#mandrake & #mandrake-linux = help for newbies
#mandrakeguru = advanced discussions
#mdk-cooker = Mandrake Cooker discussions
Re: [Cooker] Can't Compile apps - Qt error
On Mon, 18 Mar 2002 18:42:48 +1200 Bill Greenwood <[EMAIL PROTECTED]> wrote: > > Have tried to compile several apps, and while running configure, it > crashes on Qt. > > Fully freshened to latest Cooker, and latest qt libs of course: > libqt2-2.3.1-29mdk.i586.rpm > libqt2-devel-2.3.1-29mdk.i586.rpm > > The error it gives is: > > ...snip... > Trying to use gcc3? -- Grimau Lysik'an, the Bionic Elf --- Mandrake on irc.openprojects.net: #mandrake & #mandrake-linux = help for newbies #mandrakeguru = advanced discussions #mdk-cooker = Mandrake Cooker discussions
Re: [Cooker] rpmdrake behaviour
On 17 Mar 2002 12:29:06 +0100 Stefan Jourdan <[EMAIL PROTECTED]> wrote: > Hello > > I was wondering something > > Why all the packages aren't listed in rpmdrake ? > > Is that me or is that normal ? > > ie : a lot of people would want to use Audacity (sound editor), and it's > not listed under /Multimedia > > Same for hundreds of packages. > > Maybe I'm not aware of something very well known here ... > The flat list. -- Grimau Lysik'an, the Bionic Elf --- Mandrake on irc.openprojects.net: #mandrake & #mandrake-linux = help for newbies #mandrakeguru = advanced discussions #mdk-cooker = Mandrake Cooker discussions
Re: [Cooker] http://symantec.com causes weird X effects in Galeon/Mozilla
On Fri, 8 Mar 2002 22:56:44 -0800 (PST) SI Reasoning <[EMAIL PROTECTED]> wrote: > Go to http://symantec.com/ and watch the light show on > X. Warning to those who are epilectic or are prone to > being hypnotised. I certainly hope that this is not > the intended effect! This effect is found in > Galeon/Mozilla but not in Konqueror. > ?? Looked perfectly normal to me in Galeon. -- Grimau Lysik'an, the Bionic Elf --- Mandrake on irc.openprojects.net: #mandrake & #mandrake-linux = help for newbies #mandrakeguru = advanced discussions #mdk-cooker = Mandrake Cooker discussions
Re: [Cooker] Mandrake Linux Cooker-i586 20020307 3:18
On Sat, 09 Mar 2002 14:18:34 +1100 Ron Stodden <[EMAIL PROTECTED]> wrote: > Re: Mandrake Linux Cooker-i586 20020307 3:18 > ... > > 7. Despite a wheel mouse being indicated and tested, the necessary > imwheel RPM is not being installed. The wheel therefore remains > inoperative. > Once imwheel is installed manually it is necessary to reboot the entire > system - this violates Linux conventions. imwheel is not only unnecessary for most systems, it actually hinders proper wheel response. -- Grimau Lysik'an, the Bionic Elf --- Mandrake on irc.openprojects.net: #mandrake & #mandrake-linux = help for newbies #mandrakeguru = advanced discussions #mdk-cooker = Mandrake Cooker discussions
Re: [Cooker] icons require sound? Dependency wars
>From: Stefan van der Eijk <[EMAIL PROTECTED]> > >Yura Gusev wrote: > >>On Sat, 20 Oct 2001, Stefan van der Eijk wrote: >> >>>Let's see... the buildoutput is available at: >>> >>>http://cm61-10-20-87.hkcable.com.hk/build/cooker/i586/OK/kups-1.1-11mdk.src.rpm.txt >>> >>>The only place in the buildoutput where I can find mcopidl is: >>> >>>checking for dcopidl2cpp... /usr/bin/dcopidl2cpp >>>checking for mcopidl... /usr/bin/mcopidl >>>checking for kdb2html... /usr/bin/kdb2html >>> >>>So it probably doesn't use this program to Build the application either. >>>But if i leave out the BuildRequires, and arts isn't installed the >>>package won't be rebuilt, because it will hang on the ./configure. >>> >>>What should I do? >>>1/ Keep the BuildRequires and just let it be; >>>2/ Remove the BuildRequires, and have a broken package (at least on my >>>rebuilding system); >>>3/ Patch the source to let ./configure not check for mcopidl so we can >>>drop the BuildRequires: arts. This means there is another patch to make >>>& maintain and figuring all this out takes time. Feel free to submit >>>such a patch and I'll put it in; >>>4/ Report a bug to the authors of the kups software and when the bug is >>>fixed drop the BuildRequires: arts; >>> >> >>4 is the best solution. I think they just used generic kde make file. So >>it's up to them to fix this problem. >> >Yes. > >A lot of other kde software also uses this strategy. The kde-i18n-* and >koffice-i18n-* packages are BuildRequire arts and kdelibs > That doesn't make it right. Bad software engineering should not be propagated, no matter who started it. ___ Grimau Lysik'an, The Bionic Elf _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: [Cooker] icons require sound? Dependency wars
>From: Stefan van der Eijk <[EMAIL PROTECTED]> >Grimau Lysik'an wrote: > >>>From: Stefan van der Eijk <[EMAIL PROTECTED]> >>> >>>>#2) You say nothing about the reason. >>> >>> >>>./configure was looking for /usr/bin/mcopidl, and couldn't find it. >>> >>>[stefan@taz OK]$ urpmf /usr/bin/mcopidl >>>arts:/usr/bin/mcopidl >>> >>>So I added BuildRequires arts. >> >> >>This is what I am talking about - adding a requirement just to make it >>work. Do you know that mcopidl is REALLY needed, or are you just >>trying to make ./configure happy? > >Let's see... the buildoutput is available at: > >http://cm61-10-20-87.hkcable.com.hk/build/cooker/i586/OK/kups-1.1-11mdk.src.rpm.txt > >The only place in the buildoutput where I can find mcopidl is: > >checking for dcopidl2cpp... /usr/bin/dcopidl2cpp >checking for mcopidl... /usr/bin/mcopidl >checking for kdb2html... /usr/bin/kdb2html > > >So it probably doesn't use this program to Build the application either. >But if i leave out the BuildRequires, and arts isn't installed the >package won't be rebuilt, because it will hang on the ./configure. > >What should I do? >1/ Keep the BuildRequires and just let it be; >2/ Remove the BuildRequires, and have a broken package (at least on my >rebuilding system); >3/ Patch the source to let ./configure not check for mcopidl so we can >drop the BuildRequires: arts. This means there is another patch to make >& maintain and figuring all this out takes time. Feel free to submit >such a patch and I'll put it in; >4/ Report a bug to the authors of the kups software and when the bug is >fixed drop the BuildRequires: arts; Obviously 4. If you have the time, doing 3 while waiting for it to be fixed would be good, but I gather you don't. > >>If mcopidl is really needed, then it's obviously NOT just an arts >>thing and should be taken out and put in a more reasonable place. (I >>know that isn't what you are working on at the moment - but someone >>should be). > >How about we take a different look at this? The mcopidl program, in wich >package should it reside? The following files are in RedHat's Rawhide >art s package: > >[stefan@taz RPMS]$ rpm -qipl arts-2.2.1-1.alpha.rpm | grep bin >/usr/bin/artscat >/usr/bin/artsd >/usr/bin/artsdsp >/usr/bin/artsplay >/usr/bin/artsshell >/usr/bin/artswrapper > >And for cooker: > >[stefan@taz RPMS]$ rpm -qpl arts-2.2.1-8mdk.i586.rpm >libarts2-2.2.1-8mdk.i586.rpm libarts2-devel-2.2.1-8mdk.i586.rpm | sort | >grep bin >/usr/bin/artscat >/usr/bin/artsc-config >/usr/bin/artsd >/usr/bin/artsdsp >/usr/bin/artsplay >/usr/bin/artsshell >/usr/bin/artswrapper >/usr/bin/mcopidl > >The mcopidl binary seems to be in a differen package on cooker. In >Rawhide mcopidl can be found in: kdelibs-sound-devel-2.2.1-1.alpha.rpm. >Cooker doesn't have kdelibs-sound-devel anymore... > >Please advise. Depends on if mcopidl is used anywhere else. If it's always used with arts and only arts (not including incorrectly built configure scripts) then leave it where it is. ___ Grimau Lysik'an, The Bionic Elf _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: [Cooker] icons require sound? Dependency wars
>From: Stefan van der Eijk <[EMAIL PROTECTED]> >>#2) You say nothing about the reason. > >./configure was looking for /usr/bin/mcopidl, and couldn't find it. > >[stefan@taz OK]$ urpmf /usr/bin/mcopidl >arts:/usr/bin/mcopidl > >So I added BuildRequires arts. This is what I am talking about - adding a requirement just to make it work. Do you know that mcopidl is REALLY needed, or are you just trying to make ./configure happy? If mcopidl is really needed, then it's obviously NOT just an arts thing and should be taken out and put in a more reasonable place. (I know that isn't what you are working on at the moment - but someone should be). > >>#3) All requirements and the "why" of them should be documented for >>any serious development project. If you can't document why you >>included the requirement then it's not likely you know. And if you >>don't know, then don't put it in there. Adding deps just cause it >>"makes it work" is not software development, it's playing around. > >The thing is, you can document all of this stuff, produce tonnes of >comments. Will it serve a purpose? If you feel documenting everything in >great detail serves a pupose, please specify with how much detail I >should document the changes I make to the packages. > Any time you add a dependency you should say why. And "to make it work" is not a good reason. :) There are a great many books available on software development - I can guarantee that every one that mentions the subject advises in favor of documentation. It may be a pain in the butt at times, but it can save a lot of bewilderment in the future. ___ Grimau Lysik'an, The Bionic Elf _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
Re: [Cooker] icons require sound? Dependency wars
>From: Stefan van der Eijk <[EMAIL PROTECTED]> >> >>>>>>Subject: [CHRPM] mandrake_desk-8.1-21mdk >>>>>> >>>>>>- BuildRequires: arts >>>>>> >>>>>>Why does package that contains icons&backgrounds needs sound server? >>>>>> >>>>>Good question, but it does, really. >>>>> >>>>No, it doesn't. >>>> >> >>OK maybe it does. But tell me WHY kups KDE printer configuration tool >>needs it, any sober reason? To many deps is bad thing. Can we do anything >>about it or it is a linux way? >> >Is it really important? Come on, it's a BuildRequires, as in Required to >Build the package. It doesn't say anything about the dependancies of the >binary package. > >If you really want to know why it's needed, please examine the source of >the package. > That's one of the worst answers I've seen on this list. #1) BuildRequires are important - you make light of them. #2) You say nothing about the reason. #3) All requirements and the "why" of them should be documented for any serious development project. If you can't document why you included the requirement then it's not likely you know. And if you don't know, then don't put it in there. Adding deps just cause it "makes it work" is not software development, it's playing around. ___ Grimau Lysik'an, The Bionic Elf _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
