PR: ports/175331
Submitted by: Christoph Mallon
Approved by: No objections within three weeks from any maintainer
While here, style and duplicate phrase fixes in bsdcflow pkg-descr
Submitted by: mi
- be less verbose to be more friendly to running from cron
- I've been running this script for several years now,
not Kris
- Send me a copy of the output for debugging
Feature safe: yes
which to acquire the Submitted by: line.
It should be reasonable to simply use the MAINTAINER line; unfortunately we
lose the real name and only get the email address.
to avoid running SVN multiple times with command lines like the
following:
svn co --depth empty svn+ssh://svn.freebsd.org/ports/head ports
Reported by: ak@ (on IRC)
- FIX: all progress and error output goes to fd#2 (stderr)
- FIX: at top level, properly detect commands if preceded by options
- FIX: in checkstatus(), handle ~ (obstructed versioned item)
- FIX: support blanks, leading dashes, and shell meta characters:
+ in file names, so as not to choke the script on difficult file names
+ in command line arguments, so that svn commit -m "commit message" works,
rather than complaining about an unversioned file "message".
- FIX: in checkstatus(), keep leading spaces from svn status
- FIX: in setprop(), detect egrep errors, rather than assuming "no match"
- ADD: die if "check" psvn-specific command has trailing arguments
- CHANGE: replace `...` by more concise $(...) notation
- CHANGE: take maintainership, offered by beat@.
- SPEEDUP: in checkstatus(), use shell built-ins, rather than commands
- SPEEDUP: when checking files, run svn only once, rather than for each file
- SPEEDUP: when skipping "svn rm"-ed files, use ! -e rather than head|awk
- TODO: handle long options for svn commit
- TODO: do not stomp over svn:mime-type if it's already set (binary files!)
Approved by: beat@ (maintainer)
This was required with CVS, since the category was checked out as a module, but
the directory name is used with svn.
For example:
pcvs co ports_ports_mgmt
svn co $ports/head/ports-mgmt
Submitted by: swills
Approved by: vd (maintainer)
- Make the diff output work
- Use cdiff if exists, otherwise stick with $EDITOR
- Stop trying to remove CVSROOT; hasn't been checked out since modules
support was removed by erwin
pointyhat, but is intended for pointyhat-[west|east] to be able to
remove no longer needed specialized -exp runs. (They remain in the
errorlog archive; they can merely be removed from zfs.)
Replace this test with an anti-foot-shooting measure so that you cannot
remove 'latest' unless you have already removed 'previous'.
clang". This will probably need to be trimmed down some so as to not
pessimize processing time.
At this time this change will be restricted to pointyhat-west.
- deprecate assert, chown, perl5, python, stdio, sysvipc, varargs
- add the existing nested_declaration, termios, utmp_x
While here, fix formatting.
Pointy hat to: linimon, for letting this get so far out of sync
chown, perl5, python, stdio, struct changes, sysvipc, USE_XLIB, varargs
Add the following new error types that we are now seeing:
clang-bug, cpusetsize, sem_wait
Tweak the definitions for linker_error and threads to be more accurate.
to processonelog (not yet committed):
clang
clang-bug
cpusetsize
sem_wait
The former two will show up if an -exp run is done with clang as the default
ports compiler, instead of gcc. The latter two seem to be ports regressions
in 9-CURRENT.
was handled the same as "waiting for chroot" and retried. In certain
circumstances (e.g. a prerequisite package shown as being avaialable
when it really wasn't), this would cause a package build to loop
forever.
Note to future generations: I did not write this code.
Feature safe: yes
was being done before the src tree had been mounted.
This was not a problem in the old codebase, since it simply got the
wrong src tree to start with.
This actually simplifies the code.
and client-side definitions into common.conf.
While here, slide the 7-stable release to 7.3. This was driving me
crazy while trying to debug the INDEX and duds problems.
definitions and the client-side definitions.
While here, add ARCHS_SUPPORTING_COMPAT_IA32, which is needed to get
linux emulation ports to be properly detected on head nodes that are
build from first principles (e.g. !pointyhat).
nodes that don't have /usr/src. On pointyhat, this "just happens to
work"; on a cleanly installed system like pointyhat-west, it didn't.
Add overrides for Linux compatibility (again, it "just happened to work"
on pointyhat).
Move the code that sets PORTSDIR and SRC_BASE to the server side only.
The code that overrides OSVERSION, OSREL, and BRANCH _must_ remain in
the common code.
one 'head' node, rather than just pointyhat itself.
Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf. There is
only one server.conf file. Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.
NOTE: these scripts are not yet parameterized, so this is WIP.
Feature safe: yes
one 'head' node, rather than just pointyhat itself.
Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf. There is
only one server.conf file. Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.
Several bugs are fixed and improvements are made:
- parameterize everything.
- switch to csup. (This necessitates pushing the repos down one
directory level, e.g. ports-head/ports and src/src-8. However,
this will give us the flexibility to have e.g. src/src-8.1 in
the future.)
- note that the misnomer filename 'cvsdone', which was created
here, is now changed to '.updated'.
Feature safe: yes
one 'head' node, rather than just pointyhat itself.
Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf. There is
only one server.conf file. Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.
While here, do some refactoring.
Feature safe: yes
one 'head' node, rather than just pointyhat itself.
Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf. There is
only one server.conf file. Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.
Note the change of the misnomer filename 'cvsdone' to '.updated'.
Feature safe: yes
one 'head' node, rather than just pointyhat itself.
Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf. There is
only one server.conf file. Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.
Several bugs are fixed and improvements are made:
- suppress error message if there are no logs yet.
- change the misnomer filename 'cvsdone' to '.updated'.
- fix a bug by un-escaping '_' in the timestamp.
Feature safe: yes
one 'head' node, rather than just pointyhat itself.
Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf. There is
only one server.conf file. Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.
While here, fix error messages displayed on new runs.
Feature safe: yes
one 'head' node, rather than just pointyhat itself.
Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf. There is
only one server.conf file. Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.
*very* carefully note where the exported variables are consumed.
Several bugs are fixed and improvements are made:
- the file UNAME_VERSION appears unused, so it is removed. The
information is passed in overrides to uname(1).
- parameterize arch-specific setup code.
Feature safe: yes
one 'head' node, rather than just pointyhat itself.
Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf. There is
only one server.conf file. Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.
Feature safe: yes
one 'head' node, rather than just pointyhat itself.
Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf. There is
only one server.conf file. Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.
Note the removal of the hard-coding of INDEX.N, where N has to be
a single digit, and also have no '.' in it.
Feature safe: yes
