RPM Building 101 :: Brian Stinson

Поділитися
Вставка

КОМЕНТАРІ • 8

  • @KarstenWade
    @KarstenWade 10 років тому +10

    Audio starts at 1:45. It was off at the beginning (my fault, forgot to make sure the speaker had turned the mic off mute.)

  • @ScottGarman
    @ScottGarman 8 років тому +3

    Super presentation, quite clear and kept things simple. I appreciate it!

  • @TheCentOSProject
    @TheCentOSProject  10 років тому +4

    We had an audio problem with the start of the session, audio kicks in 1:45 into the video

  • @karunabhardwaj4919
    @karunabhardwaj4919 5 місяців тому

    I have a bin file to be packaged into rpm. Is that possible

  • @TheCentOSProject
    @TheCentOSProject  10 років тому +2

    A short introduction and demo of building RPM packages using rpmbuild and mock, by Brian Stinson

  • @PatrickDGarveyt
    @PatrickDGarveyt 10 років тому +1

    In case you can't read it (I know you can't hear it, because it was not recorded), the title slide indicates the slides can be found at kan.st/1G9. I do wish speakers would learn to transcribe and store their speech text also. Good slides are not verbose enough to contain all the information in the text.

  • @avimehenwal
    @avimehenwal 4 роки тому

    Nice intro, is it so that rpmbuild is the ONLY build tools which can generate rpms? Are there any other alternatives to rpmbuild in market?

  • @Karthikreddygillela
    @Karthikreddygillela 5 років тому

    ---------------CAN ANYONE HELP ME OUT THIS---------------
    Create a rpm or Debian package.
    Package should do the following
    1. Create a folder /opt/test
    2. Any binary file say hello.bin or hello.jar
    3. Place the file /opt/test/hello.jar
    4. Set the owner root:root /opt/test/hello.jar
    5. Set the permission 755 /opt/test/hello.jar
    6. Add pre install script to print a message something like "Installing .... Package"
    7. Add post install script to print a message something like "Completed.. "
    8. Package should be installed or removed using dpkg or rpm.
    9. Create next version of the same packages by /opt/test/new.jar
    10. Package should updated using dpkg or rpm and /opt/test/hello.jar should be replace by /opt/test/new.jar

    ** Content of jar file is not important. you can create dummy jar file.

    Deliverable:
    1. RPM or DEBIAN package. 2 versions.
    2. SPEC file for rpm or Control file for debian.
    3. Pre and Post install script files if required.
    4. Test cases.