The contents of the library. so in the current directory (owner is root,
chmod 777) is changed correctly, an error, I think, only when it tries to
change the owner.
2012/8/11 Алексей Логинов <[email protected]>
> All users must write, read .so in current directory of project and in
> directory ru (de, fr, etc)!!! But it's not enough.
> All files from rpm package have owner - root!!!
> That's why error.
> 0644 - it's also error for libraries, what were made by msei18n.
> Sieghard, I don't speak about libraries from /lib, /usr/lib, etc., I
> speak about .so in current directory of project and in directory ru (de,
> fr, etc).
>
>
> 2012/8/10 Sieghard <[email protected]>
>
>> Hallo Алексей,
>>
>> Du schriebst am Fri, 10 Aug 2012 18:17:23 +0400:
>>
>> > Before copying from directory ru to project directory needs:
>> > rm -f ./project/libi18n_ru.so
>> > cp -f ./project/ru/libi18n_ru.so ./project
>>
>> How's that?
>>
>> > It's necessary, because all files from rpm package have root-chown and
>> > permissive 777.
>>
>> How's that, again? AFAIR from when I did use rpm, everything was installed
>> with correct user assignment and correct file permissions without any
>> special measures - the permissions are propagated via the archive embedded
>> within the rpm package.
>> Did you create the packaged files, and possibly the archive, under
>> Windows?
>> Or did you create it on a Windows-resident / -owned file system?
>> These tend to be mounted in such a way as to keep the file system
>> belonging
>> to root, but setting _every_ file to have every permission flag set - a
>> cruel sight for Linux users (and an unneccessary one at that, as even the
>> Windows file system drivers of Linux _can_ do _better_!).
>> If you create the packaged files regularly on a Linux file system and the
>> archive under Linux, file permissions should be correct without the need
>> for further manipulations, I think. (How else could rpm be used for system
>> distribution otherwise - think of the problems arising if a package wanted
>> to replace, e.g., some X11 libraries, first setting all of them to full
>> access for everyone... Any ol' root kit would propagate faster than any
>> Windows virus can...)
>>
>> --
>> (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
>> nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
>> -----------------------------------------------------------
>> Mit freundlichen Grüßen, S. Schicktanz
>> -----------------------------------------------------------
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> mseide-msegui-talk mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
>>
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
mseide-msegui-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
