Comments (7)
Here's my haikuports.conf for good measure:
# Example HaikuPorts configuration
#
# =============
# Installation:
# 1) cp haikuports-sample.conf ~/config/settings/haikuports.conf
#
# 2) customize your settings:
# lpe ~/config/settings/haikuports.conf
# ==================
# Tip:
#
# Put this into your ~/config/settings/profile to search for a string in all
# recipes with "inrecipe {searchstring}" and build a package with
# "hp {packagename}" (adjust your /path/to/your/haikuports/):
#
# function inrecipe { grep -n $1 /path/to/your/haikuports/*/*/*.recipe; }
# export -f inrecipe
#
# alias hp="haikuporter -S -j8 --get-dependencies --no-source-packages"
# ==================
# Required settings:
#
# --------------
# TREE_PATH:
# The full path to your cloned haikuports tree.
TREE_PATH="/Data/Code/haikuports"
# --------------
# PACKAGER:
# Your name and email
PACKAGER="EMAUL <[email protected]>"
# ==================
# Optional settings:
# --------------
# VENDOR:
# Sets a custom VENDOR tag that will be inserted into all built packages
# ("Haiku Project" by default).
#VENDOR="Haiku Project"
# --------------
# ALLOW_UNTESTED:
# Allow build of untested recipes. '?x86' for example
ALLOW_UNTESTED="yes"
# --------------
# ALLOW_UNSAFE_SOURCES:
# Allow building from unsafe sources. Setting this to yes allows
# downloading sources for which there is no possibility to check if they
# have been corrupted or tampered with.
#
# Only set this to yes if you really need this and know what you're doing,
# for example if you want to build recipes for development versions that
# fetch the head from a repository.
#ALLOW_UNSAFE_SOURCES="yes"
# --------------
# TARGET_ARCHITECTURE:
# The primary architectures you wish to compile recipes for.
# Defaults to the current primary platform.
#TARGET_ARCHITECTURE="x86_gcc2"
# --------------
# SECONDARY_TARGET_ARCHITECTURES:
# Secondary platforms you wish to build packages for (one per line)
# Example is x86 (gcc4) packages on a x86_gcc2 (gcc2) system
# Default is no secondary target architectures.
#SECONDARY_TARGET_ARCHITECTURES="x86"
from haikuporter.
What's 5cecf6a0? I get a 404 for that commit.
from haikuporter.
I get the same problem. This also blocks the boostrap build.
Problematic commit seems to be 5be7f1a
before: haikuporter builds source packages by default so --create-source-packages
option is not needed (but also it results in error if we specify it explicitly)
after: haikuporter does not build source packages by default and we can't change this behavior with --create-source-packages
as that results in the umount error
from haikuporter.
For this to work currently you need
CREATE_SOURCE_PACKAGES="yes"
in haikuports.conf.
It looks like I missed some cases, normally the source package should be enabled if you have either this option, or one of the command line options that results in creating a source package. Both shouldn't be needed, but it doesn't work as expected.
The condition at line 1055 looks particularly suspicious as it 'and's the config file option with the other conditions. Maybe try something like this?
if (not haveSourcePackage and not keys['DISABLE_SOURCE_PACKAGE']
and not basedOnSourcePackage
and (Configuration.shallCreateSourcePackages()
or not getOption('noSourcePackages')))
I am not sure if this is right, either. This check is too complicated for me to understand what it does.
from haikuporter.
I have to admit that I'm a bit confused. The command line help prints out the following when invoked as haikuporter --help
:
--create-source-packages
build only the (regular) source packages
--create-source-packages-for-bootstrap
build only source packages as required by thebootstrap
image
The --create-source-packages-for-bootstrap
option is used during the bootstrap procedure when creating the 'rigged' source packages (which we don't really use) but it also needs regular source packages for the *_bootstrap recipes, and I'm not sure if we can rely on haikuporter.conf during bootstrapping. So how do we enable source package creation then, if not with the --create-source-packages
option?
from haikuporter.
The command-line options should just work, but the commit introducing the option in haikuports.conf broke them. The option in haikuports.conf is meant to disable source packages only in the normal case (when --create-source-package is not specified), but I did not write the conditions the right way, and it doesn't work.
from haikuporter.
Note that you need to delete/regenerate the dependency info files in haikuports/repository for his fix to work.
from haikuporter.
Related Issues (20)
- [buildmaster] Only rename downloaded files from builder after all downloads succeed
- Skip creation of git repository if a recipe contains no patches or PATCH function HOT 5
- 'meson setup <builddir>' fails in recipes HOT 1
- Using fixCMake doesn't work as expected. HOT 1
- Warning: POLICY ERROR: no matching self provides for "libart_lgpl_devel"
- Explicitly state which dependency could not be satisfied (or why) HOT 4
- buildmaster needs to leverage object storage HOT 23
- Use python packaging.Version to handle versioning inside HaikuPorter instead of custom solution HOT 7
- Changes committed to the master without PR HOT 1
- Cannot clone repository properly on MacOS HOT 16
- Using multiple underscores in recipe name/port name doesn't work for secondary architecture (32bit) HOT 3
- [enhancement] Add RSS/Atom feed for failed builds (skipped ones too?).
- Block builds from creating/deleting users/groups HOT 6
- pip3 install no longer adds executable to path HOT 6
- Reintroduce the lib:libstdc++ dependency in haikuporter
- can only concatenate str on --why
- Haikuporter makes too many assumptions about directories existing HOT 2
- When the PATCH function fails, haikuporter resets to ORIGIN, removing patchset commits
- Draft new tagged release? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from haikuporter.