[cs615asa] HW2
Dainong Ma
dma2 at stevens.edu
Mon Mar 10 08:51:06 EDT 2014
Thank you for your information, next time I will pay more attention to what
I do and try my best to get to understand every step of doing homework. And
also I will redo my HW2 so that I can learn something that I should know
before.
On Sun, Mar 9, 2014 at 8:21 PM, Jan Schaumann <jschauma at stevens.edu> wrote:
> Hello,
>
> I've just sent out grade for HW2. If you have not received your grade,
> please contact me ASAP.
>
> A few general notes:
>
> - please do not use Microsoft Word; poorly formatted and bloated
> end-result. Use a Unix text editor (vi, emacs, nano, pico, ...) to
> write your documentation.
>
> - the license the software is made available under is the MIT license;
> you cannot just randomly change this to any string you like
>
> - your document needs to be precise; a user should be able to read your
> documentation and be able to create the package. You cannot leave out
> necessary steps.
>
> - you must explicitly note all sources from which you've taken input; if
> you found a .spec file for statsd elsewhere, you MUST NOT submit this
> without commentary as your own work
>
> - you should show that you've put some thought into where to install the
> files; dumping everything under any given prefix is not the right
> solution
>
> - you should not create an architecture specific (i686/amd64/x86_64/...)
> pakage; the software includes no architecture-specific (ie compiled)
> files, so it should be a 'noarch' package
>
> - the package has no build requirements; the only runtime requirement is
> 'nodejs'. This is different from another 'node' package
>
> - you do not need 'wget'; the system provides the curl(1) command, which
> you should be comfortable using. *If* you require the 'wget' command,
> then your documentation needs to note that it needs to be installed.
>
> - if you want to add additional files to the RPM (perhaps because some
> other spec file on the internet does so, or because you have seen some
> other website say so), then you need to explain in detail what the
> contents are and why you need them
>
>
> The most important takeaways for you is to make sure to be _precise_ in
> your documentation, to reference any work your submission is based on,
> and to actually understand what you are doing. That is, if you just
> search the internet for existing samples and then copy and paste them
> into something that eventually yields the desired end-result, you will
> not have learned anything.
>
> In addition, just because it's on the internet doesn't mean it's
> correct. A simple spec file that you created yourself may well be
> better and more correct than anything that looks advanced and clever but
> does not actually work.
>
> -Jan
> _______________________________________________
> cs615asa mailing list
> cs615asa at lists.stevens.edu
> https://lists.stevens.edu/mailman/listinfo/cs615asa
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.stevens.edu/mailman/private/cs615asa/attachments/20140310/260cd55d/attachment.html>
More information about the cs615asa
mailing list