Hi Sergei,

It's all about building a package on a virgin FreeBSD installation (the fact 
that it is a VM is irrelevant ... they just come in handy ... it's not about 
building a distro).

We mainly use Linux but we want to include as many Unix platforms as possible, 
e.g. *BSD. That includes making packaging as straightforward as possible 
(within reason) - in this case for you as the port maintainer. 

Hope that clarifies things.

Ah yes, +1 for adding the .NOTPARALLEL rule to the Makefile. :-)

Cheers

  Andreas

-- 
Andreas Leibl, RSTC Ltd
Registered in England no: 6306790
VAT Registration no: 901 2682 54
Registered Office address: Gifford House, Burton Row, Brent Knoll, Highbridge, 
TA9 4BX, United Kingdom




On 5 Aug 2014, at 16:00, Sergei Vyshenski <[email protected]> wrote:

> Hi Martin,
> 
> On 05.08.2014 15:30, Martin Bartosch wrote:
>> GNU Make can be instructed to ignore the parallel make option using the 
>> .NOTPARALLEL pseudo target.
>> 
>> Can you try adding the rule
>> 
>> .NOTPARALLEL: $(MO_TRANSLATIONS)
>> 
>> to the Makefile and retry the build?
> 
> Yes, this alternative works ok. Maybe it is worth to add this rule to 
> the code.
> 
>> Different question: can you give a FreeBSD newbie a very brief overview of 
>> what is necessary
>> to reproduce the package build on a virgin FreeBSD VM? I am considering 
> using Vagrant and a
>> FreeBSD base box to try it out myself.
> 
> This could be a long story.
> It could be made shorter if you let me understand what is your goal.
> What for do you want to build a package?
> Package for oxi or something else?
> Why do you mix package building with the use of VM?
> 
> FreeBSD ports (aka source packages) and FreeBSD packages (aka binary 
> packages) are meant to be blessed by the core team and distributed with 
> the base FreeBSD system, and should be operable by a user with 
> not-very-high knowledge about what she is doing.
> 
> Preparing of ports/packages are the domain of the so called port 
> maintainers (me being one of them). They are supposed to follow very 
> complicated set of FreeBSD rules about system building and organization.
> 
> If you just want to install some software (which is not yet 
> ported/packaged) for yourself, then your choice is a general unix 
> procedure, like configure, make, make install -- that is without any 
> porting and packaging.
> 
> All the best, Sergei
> 
> ------------------------------------------------------------------------------
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls. 
> Build a bridge from your legacy apps to the future.
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> _______________________________________________
> OpenXPKI-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openxpki-devel


------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
OpenXPKI-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-devel

Reply via email to