[cs615asa] build install and file sections

John Scire jscire at stevens.edu
Mon Feb 17 20:10:21 EST 2014


As for what files we need to package in, we only need the files 
necessary for it to run and the documentation, correct? We can leave out 
the other misc. files/directories in the statsd source tarball?

Thanks again,
John Scire

On 2/17/2014 5:30 PM, nbevacqu wrote:
> I think I managed to answer all of your questions below. Let me know 
> if I accidentally forgot one.
>
>> I am reasonably sure from the documentation I have found that for this
>> exercise the build section is not needed. There is no make file or
>> anything else to build. Is there anything else to do in this section
>> besides:
>>
>> %build
>> echo "nothing to build"
>
> I left build blank since the code is interpreted by nodejs, not compiled.
>
>> Clone the project ( this is take care of in the prep section)
>
> You shouldn't clone the project here as it introduces an unnecessary 
> dependence on github. Instead, you should clone the project and create 
> your own .tar.gz file to hold all the source code (minus the .git 
> folder and .gitignore file of course). You can then place that archive 
> inside the SOURCES directory.
>
>> Create a config file from exampleConfig.js and put it somewhere
>> (should the install section create this or just use this)
>
> For the config file, I kept the example config file and just placed it 
> in the appropriate place after renaming it. I did not include any code 
> to run node in my spec file (ex: node stats.js config.js). I put my 
> config file in /etc/statsd and the code/documentation inside 
> /usr/share/statsd and /usr/share/doc/statsd respectively.
>
>> Do we just have to put the executable in /usr/bin and make sure that
>> the dependencies are taken care of? Should we take the default
>> configuration and put it into the same dir as statsd?
>
> The executable included in the bin directory assumes that the 
> executable is in the same folder at the lib directory. As such, I did 
> not install it in /usr/bin. Since the executable just ran node 
> stats.js, I didn't bother to include this file at all for the time being.
>
>> Finally for the files section we should be specifying where everything
>> goes but do we specify every file or do we just specify the special
>> ones to treat differently during build time?
>
> You have to move the files themselves into the appropriate place 
> during the install process. Under the %files section, list all the 
> files/directories you installed.
>
>
> Sincerely,
> Nicholas Bevacqua
> _______________________________________________
> cs615asa mailing list
> cs615asa at lists.stevens.edu
> https://lists.stevens.edu/mailman/listinfo/cs615asa



More information about the cs615asa mailing list