On 6 Feb 2017, at 02:57, Ryan Schmidt wrote:
> If you are using a git checkout of the complete ports tree (like I am), then
> you have no use for the rsync tarball anymore.
Not yet, but I might give it a try. Any caveats worth mentioning or adding to
the guide?
On Feb 3, 2017, at 07:14, db wrote:
>
> I guess I could use a git checkout for everything. I wonder how would that
> work with the rsync tarball, as it seems not to be documented in the guide.
If you are using a git checkout of the complete ports tree (like I am), then
you have no use for the
I guess I could use a git checkout for everything. I wonder how would that work
with the rsync tarball, as it seems not to be documented in the guide.
Otherwise, I could parse the sources by port directory, list them, rename the
Portfile I want to override and re-index.
On 2 Feb 2017, at 17:24,
Hi,
On 02/02/17 16:16, db wrote:
On 2 Feb 2017, at 16:34, Mojca Miklavec wrote:
If you only want to do it once, you can cd to the folder with the port
that you want to use and run "sudo port ..." from there.
Hmm…no, I thought I could mark the ports' default priority/availability,
something
On 2 Feb 2017, at 16:34, Mojca Miklavec wrote:
> If you only want to do it once, you can cd to the folder with the port
> that you want to use and run "sudo port ..." from there.
Hmm…no, I thought I could mark the ports' default priority/availability,
something like setrequested with leaves.
I
On 2 February 2017 at 16:02, db wrote:
> I already have a local repo — I'd like a port in the rsync tree to
> exceptionally override the local one (higher preference) while keeping both
> in place.
If you only want to do it once, you can cd to the folder with the port
that you want to use and r
I already have a local repo — I'd like a port in the rsync tree to
exceptionally override the local one (higher preference) while keeping both in
place.
On 2 Feb 2017, at 14:31, Mojca Miklavec wrote:
> On 2 February 2017 at 09:17, db wrote:
>> How can I override a local portfile without deleti
On 2 February 2017 at 09:17, db wrote:
> How can I override a local portfile without deleting it? I want to keep some
> ports locally, for example, after I submitted a new, locally tested port that
> made it in the repo, or when I want to keep an older portfile until I fully
> tested the latest
On 2017-02-02 09:17, db wrote:
> How can I override a local portfile without deleting it? I want to keep some
> ports locally, for example, after I submitted a new, locally tested port that
> made it in the repo, or when I want to keep an older portfile until I fully
> tested the latest version
How can I override a local portfile without deleting it? I want to keep some
ports locally, for example, after I submitted a new, locally tested port that
made it in the repo, or when I want to keep an older portfile until I fully
tested the latest version of an application.
10 matches
Mail list logo