translation missing: en.flash.savingtranslation missing: en.flash.errorgettext0.19.8.1QmQGjhRYdiZUNTprxVbuJjub1zP3jN2SfKNE837bK8qcZK5dt7poNJdJaNqZoFeXgaWpiApfDrmz
QmQGjhRYdiZUNTprxVbuJjub1zP3jN2SfKNE837bK8qcZK5dt7poNJdJaNqZoFeXgaWpiApfDrmz
Build
This panel views the builds of the artifact.
Many objects can elect to have a "build" phase. This is a transforative action that takes the content of the object and produces a useful result that is considered the actual representation of the object.
For software, this is the actual build or compilation step. Source code is the data comprising the object in the archive. The build step turns the text source code into a machine usable binary that would actually be used to invoke the software. That build step can be described in the object and then deployed to produce such a binary. The log and resulting files can be explored here.
Any completed build of an object will show up here. Such a build was a deployment of the object in some form. That is, much like running an object, it had to have a proper environment created for it consisting of the object (source code, etc) and dependencies (the compiler it needs, etc). Builds might use historic components also themselves archived in the system. To ensure these are more properly repeatable, each build records exactly the software and data used in that environment.
When you select a build, it will present you with a description of that environment in what is called a task. The manifest itself is the metadata for the task which lists the dependencies. Interacting with that list allows you to view the dependencies from the point of view of the version used in the build.
Other metadata is listed as well. The identifier for the build is simply the identifier of the task (which is itself an object in the archive.) The hash of all the resulting files and logs to uniquely and verifiably identify the build anywhere. The time elapsed to produce the build at the time it was built, which is itself listed as the date.
You can see all historic builds in the queue side-panel. Each will be listed by their date of deployment.
You can invoke a new build by going to the "New" tab or by selecting "Queue" in the queue side-panel. This gives you a listing very similar to that in the "Run" panel, which lists the possible environment needed to perform the build and allow you to override which artifacts and software are used to do so.
Listing /usr/share/doc/gettextHelp
This is the file listing that shows the files within directories of this current object.
When you are editing your own objects, you can perform some actions to update the files. We will discuss these actions now.
You can upload files by either dragging them into the file listing from your local machine or by using the buttons near the listing.
You can create a new file by using one of the buttons near the listing. This will allow you to give the file a name which you can then click on to open the blank file to edit it further.
You can add a new directory to organize your files by using another button near the listing. Once you press the button, you can name the directory and then click on it to traverse to this empty directory.
Note that you cannot have a directory or file with the same name in the same directory. This includes not being able to have a directory and file with the same name.
Clicking on a file in the listing will open the file. If you are editing the object, then it may open an editor for that file. Otherwise you will receive a read-only view of the file. The viewer or editor will depend on your associations for the type of file. Most text files, for instance, will open in a text editor.
The actions button to the right of each file in the listing will select further actions to be done on each file. These actions will be discussed now.
The remove action will delete the file from the current view of the object when you have such permissions.
The download action will download a copy of the file to your local machine.
The set as main action will set the given file as the main file for the object. For many objects, this has special significance. It will essentially set the
filefield of the object to the path to this file. You can refer to it in a run or build command to make the object more flexible and extensible instead of hard-coding such paths. Other objects might expect afileto be chosen when they take an object as input in a workflow. In these cases, the main file highlights which file is most important. Occam especially handles HTML documents and widgets by loading the main file as the entry point to the interactive program or document.
0 B 0 B .. 45.54 KiB text/html gettext_4.html 4.20 KiB text/html gettext_22.html 7.72 KiB text/html msgfilter.1.html 9.89 KiB text/html msgmerge.1.html 2.92 KiB text/html recode-sr-latin.1.html application/octet-stream javadoc2 43.44 KiB text/html FAQ.html 4.66 KiB text/html gettext.1.html application/octet-stream csharpdoc 8.05 KiB text/html msgcomm.1.html 66.94 KiB text/html gettext_19.html 18.25 KiB text/html gettext_3.html 48.69 KiB text/html gettext_21.html 54.94 KiB text/html gettext_11.html 4.26 KiB text/html bindtextdomain.3.html 66.08 KiB text/html gettext_8.html 13.58 KiB text/html gettext_17.html 2.14 KiB text/html gettext_14.html 10.02 KiB text/html msggrep.1.html 7.79 KiB text/html msguniq.1.html 32.21 KiB text/html tutorial.html 3.64 KiB text/html envsubst.1.html 9.25 KiB text/html msgattrib.1.html 12.22 KiB text/html msgfmt.1.html 3.81 KiB text/html gettext_23.html 28.59 KiB text/html gettext_12.html 33.22 KiB text/html gettext_10.html 6.83 KiB text/html msgconv.1.html 12.78 KiB text/html xgettext.1.html 8.46 KiB text/html msgcat.1.html 5.53 KiB text/html msginit.1.html 13.79 KiB text/html gettext_18.html 18.19 KiB text/html gettext_6.html 6.81 KiB text/html msgen.1.html 2.66 KiB text/html gettext_20.html 8.26 KiB text/html msgunfmt.1.html 11.08 KiB text/html gettext_7.html 6.20 KiB text/html gettext.3.html 101.06 KiB text/html gettext_9.html 27.91 KiB text/html gettext_5.html 7.56 KiB text/html gettext_16.html 4.11 KiB text/html gettextize.1.html 116.79 KiB text/html gettext_15.html application/octet-stream examples 26.87 KiB text/html gettext_25.html 29.46 KiB text/html gettext_1.html 2.83 KiB text/html gettext_foot.html 3.94 KiB text/html ngettext.3.html 14.80 KiB text/html gettext_2.html 71.15 KiB text/html gettext_13.html 4.74 KiB text/html ngettext.1.html 3.64 KiB text/html textdomain.3.html 1.30 KiB text/html gettext_24.html 3.28 KiB text/html autopoint.1.html 4.37 KiB text/html msgexec.1.html 4.88 KiB text/html msgcmp.1.html 31.06 KiB text/html gettext_toc.html 4.39 KiB text/html bind_textdomain_codeset.3.html Building
collectiongettextProviding
linux
x86-64
singularity-environmentLinuxBackend
singularityDispatch To
Occam ServerID
QmeJzsZRD1LT35NX2E5xkyBMnQG5yTWhQdLX8CBqneBB6K
Hash
b8283ec39adfdf17f0cbcc975356c113088a0f0c3d0836cd882c34a3240cece8
Time
3 mins 43 secs
Date
Thu, 29 Jul 2021 19:41:34 +0000
Backend
singularity
task
Task to build gettext on singularity
singularity-environment
Linux
collection
build1.0
headers
linux4.9.33
runtime
glibc2.25
runtime
g++10.3.0
library
stdc++10.3.0
library
gmp6.1.2
library
mpfr3.1.5
library
mpc1.0.3
application
gzip1.8
collection
texinfo4.9-bootstrap.s2
language
perl5.26.2
library
ncurses6.0
library
readline7.0
application
db5.3.28
application
gdbm1.13
perl-module
Encode2.89-bootstrap.s2
application
tar1.29
collection
diffutils3.5
application
file5.31
library
zlib1.2.11
language
bash4.4
collection
coreutils8.27
application
make4.2.1
application
sed4.4
collection
binutils2.29
application
flex2.6.4
application
m41.4.18
application
grep3.0
application
gawk4.1.4
collection
shadow4.5
collection
findutils4.6.0
application
which2.21
application
pkg-config0.29.2
compiler
g++10.3.0
collection
gettext
A set of tools that provide a framework to help other GNU packages produce multi-lingual messages.
- httpsproxy.archived.software
Generating tasks and queuing jobs...
