13 December 2007.
RPM weaknesses
RPM Package Manager It makes it possible to work with your computer simply and conveniently. It follows the renovations of distributivov, it makes it possible dynamically to be switched between repozitoriyami and to always be absolutely confident what files in the local machine they were changed or they became obsolete. RPM this is steep pitch v before, in comparison with the obsolete mechanisms of the propagation of the packets through the initial code. In order to obtain the working computer now there is no need for having a qualification of programmer, knowing the finesses of assembling nucleus under the different versions of compilers, searching for the lost libraries and expending is somewhat it is hour to assembling of graphic medium. However, as any system it is aimed at achievings of the specific goal, which can be always not accessible or not to be effective. I speak about not a sufficient objectivity during construction opensource of model.
Obtaining data from the external sources
The contemporary market for services, until now, did not embark completely on the path of mutual confidence with the user, and we on the previous obtain the large part of the production from the box, in which is applied the license limiting us to the majority of actions. So in particular, to the propagation of the acquired product. This problem concerns not only the question about the piracies, which certainly negative is reflected in the development of civilized program market and worthy reward of developers for their labor. By other side of this problem stands the unjustified limitation of my possibilities as legal user. But this limits work with the propriyetarnymi products and it does not make it possible to use the technologically effective solutions of control of distributivami, which so there are many in opensource association.
By other words the model, which forces to store entire information in one repozitorii already it became obsolete. First of all the presence of mirrors they do not decide the problem of distributivity, in the second contemporary products they require storage of information on the license carrier, while the tuning for such systems can be located in repozitorii of distributiva of system. Is obtained that we we come to model p2p of systems in which the carrier of protected kontenta they are users and distributiv this means of work with this kontentom. Leaves our task of building system RPM being been based on three basic components: the source of data, repozitoriy, the files of tuning.
The source of data - this any resource which contains license kontent. User in the right itself to select from where it is ready to grant to system to obtain data for distributiva. In particular this can be p2p the network, such as torrent, emule or license carrier to the compact disk.
Repozitoriy - this centralized depository of tuning and information about that what data must be obtained for the work of system. For simple data of distributivov this can be md5 sum and reference to the mirrors. For the more reliable protection and the additional checking of the integrity of source it is better to use references emule or torrent.
Configurative files - these are the collection of scripts is made it possible make it possible to adapt data for the work in current repozitorii, which include the displacement of data, the compilation of iskhodnikov or the imposition of pachey on the binary files.
As a result of this transformation of system we will obtain complete control and flexibility for constructing any distributivov of kontent containing any both closed and opened and practically satisfying all conditions of licensing.
Thus it is necessary to improve yum - support torrent, emule, dc++, cdrom. Support by standard rpm - external references. Creation of repozitoriyev concerning konfiruratsiyami and informaii to kontente the matter already of users.
For program distributivov will approach the qualification according to the type of distributiva. For example in order to establish quake3 to be required file pak0.pk3 from baseqa3, it it is possible to sign on md5, so sources with the more complete information such as DTH (dc++) or reference emule. For creating repoiztoriyev of those transferring musical compositions will approach the genre, yr, name of group and so on, furthermore codec, its version and md5 the sum of file, or DTH\.emule. In this case we will be always assured that our compact the disk, from which occurs copying data authentic!
System of checking the integrity
Besides the problem of propagation, another less is global. Unfortunately in contemporary distributivakh of those being being based on adjusting packets there is no very important possibility on the control of the state of system. Any packet can be random or umyshlenno is changed and we obtain the inefficient of system. Especially this sensitively for the packets of libraries change of which in the case of the distortion of file system they can bring to the loss of control of entire system. Greatly does not be sufficient the means of that making it possible to examine all files of system and to clearly reflect the packets of distributivov to which they they belong. Furthermore, necessary to reflect changes it is file on the disk and excess it is file, not belonging to any of the packets. In the case of detecting such differences it is necessary to present the possibility to pereustanovit' the damaged packet or to remove the lishniy\vremennyy file.
yum install amarok prodigy-discogray
Author axet to 16:46 &#y'0;
2 kommentariya(ev):
lynz comments on...
Concerning checking of integrity.
There exists rpm -.V for the verification of integrity and rpm -.tsf for explaining the belonging of halyards.
The light film Shell around this - is obtained working tool; moreover RPMDB here is sufficiently effective.
Concerning the first part. Litsenzionnosti are not admitted in RPM. moreover they are not admitted simply because RPM - low-level tranzaktsionnyy and noninteractive tool. Accordingly bindings with the the kontsiguratsiyey must to be (and by the way they are) at the stage of assembling RPM (to toyest' to similar kontenu is possible simply to lay out SPEC, where RPMbuild realizes necessary functionality), or must be introduced into more high-level tools of class yum.
13 December 2007. 23:03 &#y'0;
axet comments on...
For guaranteeing the integrity, it falls short this means itself, but not simple wrappers on shele. The fact that accessibly now is not extremely clearly, and it complicates diagnostics thus. In particular, in me already several times spoiled file system at the low level because of the careless work with it. And 4 to neznayu of means that making it possible to restore my system and to make this is clearly, besides perhaps that adjusting disk. With some craftinesses so it helps smart reinstall `.rpm of -.tsa`
The license limitations in this case no one disturb, since kontent is not extended with the packet.
13 December 2007. 23:13