Send hpx-devel mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://mail.cct.lsu.edu/mailman/listinfo/hpx-devel
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of hpx-devel digest..."


Today's Topics:

   1. Re: Moving forward with first split of the HPX    repository
      (Simberg  Mikael)


----------------------------------------------------------------------

Message: 1
Date: Fri, 17 Dec 2021 19:33:11 +0000
From: "Simberg  Mikael" <[email protected]>
Subject: Re: [hpx-devel] Moving forward with first split of the HPX
        repository
To: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"

Hi all,


We've now merged the two pull requests that split HPX into two repositories. 
While we've tried to take care of all issues in the build system, some have 
certainly been missed, and we'd greatly appreciate you trying things out and 
reporting problems that you find either here, or on either of the issue 
trackers of the two repositories.


If you are only interested in the on-node functionality of HPX (i.e. HPXLocal) 
it now lives at https://github.com/STEllAR-GROUP/hpx-local. The build system is 
largely unchanged. The most significant changes are:

- HPX_WITH_* CMake options have been renamed HPXLocal_WITH_*

- Options that only affect distributed functionality have been removed.


If you are interested in distributed functionality the repository continues to 
live at https://github.com/STEllAR-GROUP/hpx. The build system is intended to 
work exactly as before. This means that:

- The HPX build system will by default automatically download and configure a 
fixed tag of HPXLocal.

- CMake options that affect only HPXLocal will be automatically forwarded from 
HPX_WITH_* to HPXLocal_WITH_*.

- Build system-related CMake options that have equivalents for both HPX and 
HPXLocal will be forwarded from HPX to HPXLocal on first configuration (e.g. 
HPX_WITH_TESTS).


The default behaviour of HPX is to download HPXLocal. This behaviour is 
controlled by the HPX_WITH_FETCH_HPXLOCAL option. By turning it off HPX will 
instead search for an installed copy of HPXLocal. Alternatively, fetchcontent 
can be told to use a repository on the filesystem instead of downloading 
HPXLocal. This can be done by keeping HPX_WITH_FETCH_HPXLOCAL enabled, but 
setting FETCHCONTENT_SORUCE_DIR_HPXLOCAL=<path/to/hpx-local>.


Until the next HPX and first HPXLocal releases we recommend staying with the 
tagged version of HPXLocal when using HPX. This is defined by 
HPX_WITH_HPXLOCAL_TAG. After the next releases we will relax this requirement.


Finally, there are a number of pull requests open that change files in 
HPXLocal. Please get in touch with me here or IRC if you would like help with 
retargeting your pull requests to the new repository or in general with 
resolving potential conflicts. The easiest way to retarget a branch against 
HPXLocal is to add HPXLocal as a new remote on your local clone of HPX:


git remote add origin-hpx-local [email protected]:STEllAR-GROUP/hpx-local.git

git fetch origin-hpx-local


You can then in most cases rebase your branch on top of master of HPXLocal:


git rebase --onto origin-hpx-local/master origin/master <my_branch>


I additionally recommend doing this as an interactive rebase with the -i option 
to check that you are rebasing all and only the required commits from your 
branch. If your pull request targets both repositories create a new branch for 
the new pull request that will target HPXLocal before rebasing.


Thanks for your patience with this process.


Mikael

________________________________
From: [email protected] <[email protected]> 
on behalf of Simberg Mikael <[email protected]>
Sent: Thursday, November 4, 2021 11:06:02 AM
To: [email protected]
Subject: {Spam?} [hpx-devel] Moving forward with first split of the HPX 
repository


Hi all,


We're getting closer to a stage where we can go through with the initial split 
of the HPX repository into two parts: the current STEllAR-GROUP/hpx and a new 
STEllAR-GROUP/hpx-local. The pull requests for these changes are 
https://github.com/STEllAR-GROUP/hpx-local/pull/2 and 
https://github.com/STEllAR-GROUP/hpx/pull/5586. I'd appreciate any comments or 
concerns about the changes on the pull requests at this point. However, further 
adjustments can (and will likely have to) be made even after those pull 
requests are merged.


In order to make the timing of merging those PRs the least disruptive to open 
work, I've labeled all open PRs with "split: X", where X can be one of:


- distributed

- local

- docs

- config/ci/cmake


PRs labeled with "split: distributed" make changes to distributed 
functionality, i.e. things that will stay in the current hpx repository. PRs 
labeled only with "split: distributed" can be merged at any time and do not 
affect the split. PRs with "split: local" make changes to things that will be 
moved to hpx-local. PRs labeled only with "split: local" can be easily 
retargeted to the hpx-local repository. PRs with "split: docs" also only affect 
the current repository, as for the moment all documentation will live in the 
hpx repository. PRs with "split:  config/ci/cmake" may affect either repository 
and will need to be dealt with on a case-by-case basis. I'm currently mostly 
concerned with PRs labeled both "split: local" and "split: distributed", i.e. 
these PRs: 
https://github.com/STEllAR-GROUP/hpx/pulls?q=is%3Aopen+is%3Apr+label%3A%22split%3A+local%22+label%3A%22split%3A+distributed%22+.
 #5595, #5589, #5564, #5517 are close to ready and should be possible to merge 
soon. #5467 
 and #5241 still have some open issues (i.e. ones with unknown solutions). If 
possible we should try to focus on making progress on those PRs. Ideally they 
would all be merged before the split goes through, but it will still be 
possible to do them afterwards as well. The PRs will just need to be split up 
to target both repositories.


Kind regards,

Mikael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mail.cct.lsu.edu/pipermail/hpx-devel/attachments/20211217/f73ac2b8/attachment-0001.html
 

------------------------------

_______________________________________________
hpx-devel mailing list
[email protected]
https://mail.cct.lsu.edu/mailman/listinfo/hpx-devel


End of hpx-devel Digest, Vol 76, Issue 2
****************************************

Reply via email to