Sponsored Content
Operating Systems Linux Fedora Newby: How to actually update software?! Post 302868779 by Corona688 on Monday 28th of October 2013 06:39:11 PM
Old 10-28-2013
It may be available through an alternate server.

Worst case, if you do have to build it yourself, keep a list of everything it installs should you need to rm it at a later date.
 

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Help for a newby

I am new to using nawk. When I put the following line in script file test1.awk I get the results: { print NR, length($0),NF} >nawk -f test1.awk head.txt 1 63 5 2 2622 188 3 2166 155 4 3192 228 5 2679 192 ..... but if I modify the test1.awk file to look like this: BEGIN {FS = ","}... (2 Replies)
Discussion started by: placroix1
2 Replies

2. OS X (Apple)

Software Update reporting script

I need a script that gets the output of softwareupdate -al on each machine (the list of available updates) and reports how many updates are needed in total by all the machines on the network, and the results to 4 different recipients. i.e. total patches required = 12 hostname1 =4 patch(es)... (1 Reply)
Discussion started by: glev2005
1 Replies

3. SuSE

update package/software questions

Hi, In SUSE linux, it looks like that I can update the package using YAST or install the package from source. So, which way works better? Also, if i install the package of new version. Do i need to remove/delete the old version package, or I just need to change my environments and keep the old... (0 Replies)
Discussion started by: jianma
0 Replies
GO-BUILD(1)						      General Commands Manual						       GO-BUILD(1)

NAME
go - tool for managing Go source code SYNOPSIS
go build [-o output] [ build flags ] [ packages ] DESCRIPTION
Build compiles the packages named by the import paths, along with their dependencies, but it does not install the results. If the arguments are a list of .go files, build treats them as a list of source files specifying a single package. When the command line specifies a single main package, build writes the resulting executable to output. Otherwise build compiles the pack- ages but discards the results, serving only as a check that the packages can be built. The -o flag specifies the output file name. If not specified, the name is packagename.a (for a non-main package) or the base name of the first source file (for a main package). OPTIONS
The build flags are shared by the build, install, run, and test commands: -a force rebuilding of packages that are already up-to-date. -n print the commands but do not run them. -p n the number of builds that can be run in parallel. The default is the number of CPUs available. -v print the names of packages as they are compiled. -work print the name of the temporary work directory and do not delete it when exiting. -x print the commands. -compiler name name of compiler to use, as in runtime.Compiler (gccgo or gc) -gccgoflags 'arg list' arguments to pass on each gccgo compiler/linker invocation -gcflags 'arg list' arguments to pass on each 5g, 6g, or 8g compiler invocation -ldflags 'flag list' arguments to pass on each 5l, 6l, or 8l linker invocation -tags 'tag list' a list of build tags to consider satisfied during the build. See the documentation for the go/build package for more information about build tags. For more about specifying packages, see go-packages(7). For more about where packages and binaries are installed, see go-gopath(1). SEE ALSO
go-install(1), go-get(1), go-clean(1). AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others). 2012-05-13 GO-BUILD(1)
All times are GMT -4. The time now is 07:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy