Re: Porters Handbook section 4.4

[Russell Haley]

On Sun, Sep 24, 2017 at 10:02 PM, Kubilay Kocak  wrote:
> On 9/25/17 2:08 PM, Russell Haley wrote:
>> Hi,
>>
>> Section 4.3 of the porters handbook talks about making modifications
>> to a private copy of a tarball and recording the steps.
>>
>> Section 4.4 talks about changing directories into the affected ports
>> dir and running make makepatch to generate patch files.
>>
>> I am unsure how the makepatch target is supposed to find my private
>> directory. Since I was confused, I created patches, added them to the
>> port, ran make, then ran make makepatch and the system re-generated
>> new "makepatch" patches.
>
> Quite a number of new users have raised the same question on IRC.
>
>> So, my question is thus:
>>
>> To me, section 4.4 seems vague about where changes should be made,
>> which is compounded by the information in section 4.3. Can the
>> makepatch target ask for and find a private directory, or should the
>> handbook be clarified to state that the changes should be made to the
>> 'work' folder? If the later is true, I assume there is some proper
>> workflow to keep changes from being destroyed while testing?
>
> The handbook section needs to be updated to be less ambiguous with
> regard to where things should be done.
>
> I'd be happy to provide a docs committer with verbiage if they can help
> with formatting/commit.
Hi,

If you provide the verbiage, I'll attempt a patch. :)

Russ

>> If there is a section in the handbook clarifying this, please just say
>> so and I will go find it.
>>
>> Thanks!
>> Russ
>
> ./koobs
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Question: How to add a configuration file with autoplist ?

[Ben Woods]

On Mon, 25 Sep 2017 at 2:59 pm, Matthew Seaman  wrote:

> On 25/09/2017 12:10, Chris Rees wrote:
> > It's probably harmless to have a file listed twice,
>
> Listing a file twice will get you nasty-grams from the package build
> systems.
>
> Cheers,
>
> Matthew


Thanks Matthew - Interesting.

So what is the solution for this then? I am also curious.

Regards,
Ben

> --

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

libtomcrypt 1.18.0-rc4 - hopefully last RC

[Steffen Jaeckel]

Hi everyone,

I released the 4th and hopefully last Release Candidate of libtomcrypt
today.

http://www.libtom.net/news/LTC_1.18RC4/

If you have the time to build it on whatever platform, please feel free
to do it and I'd be happy to receive feedback either directly to me or
via [GitHub] or the [ML].

If you have any questions regarding the build or changes or dependencies
on the math libraries, feel free to also come back via one of the channels.

Thanks for your time!

Cheers,
Steffen


[GitHub]: https://github.com/libtom/libtomcrypt/issues/new

[ML]: https://groups.google.com/forum/#!forum/libtom
-- 
Steffen Jaeckel - s_jaec...@gmx.de
GnuPG fingerprint:  C438 6A23 7ED4 3A47 5541 B942 7B2C D0DD 4BCF F59B
My OTR key has changed on 30. Sept. 2015!
jabber: jaec...@jabber.ccc.de F052DE29 4FA9A02D 44A794E5 AE5AC0FB C5865C64
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

emulators/virtualbox-ose core dumps on builds

[Keith Hellman]

Hello all:

I'm running 
  FreeBSD 12.0-CURRENT #0 r320599: Mon Jul  3 15:34:15 UTC 2017 
  r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC 
with /usr/ports at svn r450591.  I *just* pulled a brand new ports
tree, so I'm reasonably confident it is in good shape.

I've been having problems (for the past month, over several revs)
building emulators/virtualbox-ose, sadly it looks like
toolchain components are dumping core (see attached log, with an ar.core
that probably shouldn't be there.

I've noticed that kmk_redirect -rti (the failing command) means to
accept input from stdin, but then a filename is provided next.  It
doesn't seem the command make is running pipes data into the process.

I've dug around a bit the vb-ose src tree but I cannot for the life of
me find the offending kmk_redirect -rti command or how it is generated
--- I was hoping to at least confirm that the command line provided
RuntimeR3.a.ar-script is being generated and to remove the -i spec.

I suspect someone at v...@freebsd.org would be faster at this than I.
Of course you could also tell me if I'm burrowing down a rabbit-hole
with a red-herring at the end :/

TiA for any help you can provide,
-- 
Keith Hellman #include 
khell...@mcprogramming.comfrom disclaimer import standard
khell...@mines.edugpg key 9FCF40FD
  freenode.net as mrtuple

"But VCs are mistaken to look for the next Microsoft, because no startup
can be the next Microsoft unless some other company is prepared to bend
over at just the right moment and be the next IBM."

-- http://www.paulgraham.com/gh.html


signature.asc
Description: PGP signature

Re: Question: How to add a configuration file with autoplist ?

[Matthew Seaman]

On 25/09/2017 12:10, Chris Rees wrote:
> It's probably harmless to have a file listed twice, 

Listing a file twice will get you nasty-grams from the package build
systems.

Cheers,

Matthew



signature.asc
Description: OpenPGP digital signature

Re: Question: How to add a configuration file with autoplist ?

[Helen Koike]

Hi,

On 2017-09-25 08:10 AM, Chris Rees wrote:
> On 2017-09-25 05:54, Kubilay Kocak wrote:
>> On 9/25/17 6:16 AM, Helen Koike wrote:
>>> Hi,
>>>
>>> According to
>>> https://www.freebsd.org/doc/en/books/porters-handbook/plist-config.html
>>> , I need to add a @sample macro in pkg-plist to add a configuration
>>> file.
>>>
>>> But I am also using USE_PYTHON= autoplist in my Makefile, so I don't
>>> have the pkg-plist file.
>>>
>>> Should I remove autoplist and generate the pkg-plist by hand? Or is
>>> there another way to do this?
>>>
>>> I'll need this to update the version of the package
>>> sysutils/py-google-compute-engine.
>>>
>>> Thanks
>>> Helen
>>
>> Hi Helen,
>>
>> As far as I'm aware, autoplist, PLIST_* definitions and pkg-plist
>> entries can be used cumulatively (in combination with each other) to
>> produce a correct and complete installed files lis>>

Thanks, I didn't know that.

> 
> Careful doing that!  If you do, you may find the sample file gets listed
> twice, or worse the actual config file gets listed.
> 
> If you want to view the final generated plist then in the normal ports
> directory:
> 
> % make package
> % less `make -VTMPPLIST`

Awesome, thanks a lot.

> 
> (those are backticks).
> 
> It's probably harmless to have a file listed twice, but if you list the
> actual config file it gets blown away on each update.
> 
> Cheers,
> 
> Chris
> 

Helen
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Question: How to add a configuration file with autoplist ?

[Chris Rees]

On 2017-09-25 05:54, Kubilay Kocak wrote:

On 9/25/17 6:16 AM, Helen Koike wrote:

Hi,

According to
https://www.freebsd.org/doc/en/books/porters-handbook/plist-config.html
, I need to add a @sample macro in pkg-plist to add a configuration 
file.


But I am also using USE_PYTHON= autoplist in my Makefile, so I don't
have the pkg-plist file.

Should I remove autoplist and generate the pkg-plist by hand? Or is
there another way to do this?

I'll need this to update the version of the package
sysutils/py-google-compute-engine.

Thanks
Helen


Hi Helen,

As far as I'm aware, autoplist, PLIST_* definitions and pkg-plist
entries can be used cumulatively (in combination with each other) to
produce a correct and complete installed files list



Careful doing that!  If you do, you may find the sample file gets listed 
twice, or worse the actual config file gets listed.


If you want to view the final generated plist then in the normal ports 
directory:


% make package
% less `make -VTMPPLIST`

(those are backticks).

It's probably harmless to have a file listed twice, but if you list the 
actual config file it gets blown away on each update.


Cheers,

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"